View JS28F128P33BF70_6354434.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

datasheet jul 2011 1 order number: 208034-04 numonyx ? p33-65nm flash memory 128-mbit, 64-mbit single bit per cell (sbc) datasheet product features ? high performance: ? 60ns initial access time for easy bga ? 70ns initial access time for tsop ? 25ns 8-word asynchronous-page read mode ? 52mhz with zero wait states, 17ns clock-to- data output synchronous-burst read mode ? 4-, 8-, 16-, and continuous-word options for burst mode ? 3.0v buffered programming at 1.8mbyte/s (typ) using 256-word buffer ? buffered enhanced factory programming at 3.2mbyte/s (typ) using 256-word buffer ? architecture: ? asymmetrically-blocked architecture ? four 32-kbyte parameter blocks: top or bottom configuration ? 128-kbyte main blocks ? blank check to verify an erased block ? voltage and power: ?v cc (core) voltage: 2.3v ? 3.6v ?v ccq (i/o) voltage: 2.3v ? 3.6v ? standby current: 35 a(typ) for 64-mbit, 50 a(typ) for 128-mbit ? continuous synchronous read current: 23ma (typ) at 52 mhz ? security: ? one-time programmable registers: ? 64 otp bits, programmed with unique information by numonyx ? 2112 otp bits, available for customer programming ? absolute write protection: v pp = v ss ? power-transition erase/program lockout ? individual zero-latency block locking ? individual block lock-down capability ? password access feature ? software: ? 20s (typ) program suspend ? 20s (typ) erase suspend ? basic command set and extended function interface (efi) command set compatible ? common flash interface capable ? density and packaging: ? 56-lead tsop package (128-mbit, 64-mbit) ? 64-ball easy bga package (128-mbit, 64- mbit) ? 16-bit wide data bus ? quality and reliability: ?jesd47e compliant ? operating temperature: ?40c to +85c ? minimum 100,000 erase cycles per block ? 65nm process technology
datasheet jul 2011 2 order number: 208034-04 legal lines and disclaimers information in this document is provided in connection with numonyx? products. no license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. except as provided in numonyx's terms and conditions of sale for such products, numonyx assumes no liability whatsoever, and numonyx disclaims any express or implied warranty, relating to sale and/or use of numonyx products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. numonyx products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear f acility applications. numonyx may make changes to specifications and product descriptions at any time, without notice. numonyx, b.v. may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights th at relate to the presented subject matter. the furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. designers must not rely on the absence or characteristics of any features or instructions marked ?reserved? or ?undefined.? num onyx reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. contact your local numonyx sales office or your distributor to obtain the latest specifications and before placing your product order. copies of documents which have an order number and are referenced in this document, or other numonyx literature may be obtained by visiting numonyx's website at http://www.numonyx.com . numonyx, the numonyx logo, and are trademarks or registered trademarks of numonyx, b.v. or its subsidiaries in other cou ntries. *other names and brands may be claimed as the property of others. copyright ? 2011, numonyx, b.v., all rights reserved.
datasheet jul 2011 3 order number: 208034-04 p33-65nm sbc contents 1.0 functional description ............................................................................................... 5 1.1 introduction ....................................................................................................... 5 1.2 overview ........................................................................................................... 5 1.3 memory maps ..................................................................................................... 6 2.0 package information ................................................................................................. 7 2.1 56-lead tsop..................................................................................................... 7 2.2 64-ball easy bga package .................................................................................... 8 3.0 ballouts ................................................................................................................... 10 4.0 signals .................................................................................................................... 12 5.0 bus operations ........................................................................................................ 14 5.1 read ............................................................................................................... 14 5.2 write ............................................................................................................... 14 5.3 output disable .................................................................................................. 15 5.4 standby ........................................................................................................... 15 5.5 reset............................................................................................................... 15 6.0 command set .......................................................................................................... 16 6.1 device command codes ..................................................................................... 16 6.2 device command bus cycles .............................................................................. 18 7.0 read operation ........................................................................................................ 20 7.1 asynchronous page-mode read ........................................................................... 20 7.2 synchronous burst-mode read............................................................................ 20 7.3 read device identifier........................................................................................ 21 7.4 read cfi .......................................................................................................... 21 8.0 program operation .................................................................................................. 22 8.1 word programming ........................................................................................... 22 8.2 buffered programming ....................................................................................... 22 8.3 buffered enhanced factory programming.............................................................. 23 8.4 program suspend .............................................................................................. 25 8.5 program resume............................................................................................... 26 8.6 program protection............................................................................................ 26 9.0 erase operation ....................................................................................................... 27 9.1 block erase ...................................................................................................... 27 9.2 blank check ..................................................................................................... 27 9.3 erase suspend .................................................................................................. 28 9.4 erase resume................................................................................................... 28 9.5 erase protection ................................................................................................ 28 10.0 security ................................................................................................................... 29 10.1 block locking.................................................................................................... 29 10.2 selectable otp blocks ........................................................................................ 31 10.3 password access ............................................................................................... 31 11.0 status register ........................................................................................................ 32 11.1 read configuration register................................................................................ 33 11.2 one-time programmable (otp) registers ............................................................. 40 12.0 power and reset specifications ............................................................................... 43 12.1 power-up and power-down................................................................................. 43 12.2 reset specifications........................................................................................... 43
p33-65nm datasheet jul 2011 4 order number: 208034-04 12.3 power supply decoupling ....................................................................................44 13.0 maximum ratings and operating conditions ............................................................45 13.1 absolute maximum ratings .................................................................................45 13.2 operating conditions..........................................................................................45 14.0 electrical specifications ...........................................................................................46 14.1 dc current characteristics ..................................................................................46 14.2 dc voltage characteristics ..................................................................................47 15.0 ac characteristics ....................................................................................................48 15.1 ac test conditions.............................................................................................48 15.2 capacitance ......................................................................................................49 15.3 ac read specifications .......................................................................................49 15.4 ac write specifications .......................................................................................54 15.5 program and erase characteristics .......................................................................58 16.0 ordering information ...............................................................................................59 a supplemental reference information .......................................................................60 a.1 common flash interface .....................................................................................60 a.2 flowcharts ........................................................................................................72 a.3 write state machine ...........................................................................................81 b conventions - additional documentation .................................................................85 b.1 acronyms .........................................................................................................85 b.2 definitions and terms ........................................................................................85 c revision history .......................................................................................................87
datasheet jul 2011 5 order number:208034-04 p33-65nm sbc 1.0 functional description 1.1 introduction this document provides information about the numonyx ? p33-65nm single bit per cell (sbc) flash memory and describes its features, operations, and specifications. p33-65nm sbc device is offered in 64-mbit and 128-mbit densities. benefits include high-speed interface nor device, and support for code and data storage. features include high-performance synchronous-burst read mode, a dramatical improvement in buffer program time through larger buffer size, fast asynchronous access times, low power, flexible security options, and two industry-standard package choices. p33-65nm sbc device is manufactured using 65nm process technology. 1.2 overview this family of devices provides high performance at low voltage on a 16-bit data bus. individually erasable memory blocks are sized for optimum code and data storage. upon initial power-up or return from reset, the device defaults to asynchronous page- mode read. configuring the rcr enables synchronous burst-mode reads. in synchronous burst mode, output data is synchronized with a user-supplied clock signal. a wait signal provides an easy cpu-to-flash memory synchronization. in addition to the enhanced architecture and interface, the device incorporates technology that enables fast factory program and erase operations. the device features a 256-word buffer to enable optimum programming performance, which can improve system programming throughput time significantly to 1.8mbyte/s. the p33-65nm sbc device supports read operations with vcc at 3.0v, and erase and program operations with vpp at 3.0v or 9. 0v. buffered enhanced factory programming provides the fastest flash array programmi ng performance with vpp at 9.0v, which increases factory throughput. with vpp at 3.0v, vcc and vpp can be tied together for a simple, ultra low power design. in addition to voltage flexibility, a dedicated vpp connection provides complete data protection when vpp v pplk . the command user interface is the interface between the system processor and all internal operations of the device. an internal write state machine automatically executes the algorithms and timings necessary for block erase and program. a status register indicates erase or program completion and any errors that may have occurred. an industry-standard command sequence invokes program and erase automation. each erase operation erases one block. the erase suspend feature allows system software to pause an erase cycle to read or program data in another block. program suspend allows system software to pause programming to read other locations. data is programmed in word increments (16 bits). the one-time-programmable (otp) register allows unique flash device identification that can be used to increase system security. the individual block lock feature provides zero-latency block locking and unlocking. the p33-65nm sbc device adds enhanced protection via password access mode which allows user to protect write and/or read access to the defined blocks. in addition, the p33-65nm sbc device could also provide the full-device otp permanent lock feature.
p33-65nm datasheet jul 2011 6 order number: 208034-04 1.3 memory maps figure 1: p33-65nm memory map (64-mbit and 128-mbit densities) 16- kword block 64- kword block 16- kword block bottom boot word wide (x16) mode 7f0000 7fffff 000000 ? 003fff 64- kword block 3f0000 3fffff 1 0 130 128- mbit a<23:1> 128- mbit 16- kword block 16- kword block 64- kword block 64- kword block 004000 ? 007fff 008000 ? 00bfff 00c000? 00ffff 010000 ? 01ffff 020000 ? 02ffff 2 3 4 5 66 16- kword block 16- kword block top boot word wide (x16) mode 64- kword block 128 127 16- kword block 16- kword block 64- kword block 64- kword block 129 130 0 1 126 000000 ?00ffff 010000 ?01ffff 7f 0000 ? 7f4000 ?7f7000 7f8000 ? 7fbfff 7fc000 ? 7fffff 7e0000 ? 7effff 64-mbit ? ? a<22:1> 64-mbit 128-mbit a<23:1> 128- mbit 16- kword block 16- kword block top boot word wide (x16) mode 64- kword block 64 63 16- kword block 16- kword block 64- kword block 64- kword block 65 66 0 1 62 000000 ?00ffff 010000 ?01ffff 3f0000 ? 3f3fff 3f4000 ? 3f7fff 3f8000 ? 3fbfff 3fc000 ? 3fffff 3e0000 ? 3effff a<22:1> 64-mbit 64 -mbit 7f3fff
datasheet jul 2011 7 order number:208034-04 p33-65nm sbc 2.0 package information 2.1 56-lead tsop figure 2: tsop mechanical specifications table 1: tsop package dimensions (sheet 1 of 2) product information symbol millimeters inches min nom max min nom max package height a - - 1.200 - - 0.047 standoff a 1 0.050 - - 0.002 - - package body thickness a 2 0.965 0.995 1.025 0.038 0.039 0.040 lead width (4) b 0.170 0.220 0.270 0.0067 0.0087 0.0106 lead thickness c 0.100 0.150 0.200 0.004 0.006 0.008 package body length d 1 18.200 18.400 18.600 0.717 0.724 0.732 package body width e 13.800 14.000 14.200 0.543 0.551 0.559 lead pitch e - 0.500 - - 0.0197 - terminal dimension d 19.800 20.00 20.200 0.780 0.787 0.795 lead tip length l 0.500 0.600 0.700 0.020 0.024 0.028 a 0 l detail a y d c z pin 1 e d 1 b detail b see detail a e see detail b a 1 seating plane a 2 see note 2 see notes 1 and 3
p33-65nm datasheet jul 2011 8 order number: 208034-04 2.2 64-ball easy bga package lead count n - 56 - - 56 - lead tip angle 0 3 5 0 3 5 seating plane coplanarity y - - 0.100 - - 0.004 lead to package offset z 0.150 0.250 0.350 0.006 0.010 0.014 notes: 1. one dimple on package denotes pin 1. 2. if two dimples, then the larger dimple denotes pin 1. 3. pin 1 will always be in the upper left corner of the package, in reference to the product mark. 4. for legacy lead width, 0.10mm(min), 0.15mm(typ) and 0.20mm(max). table 1: tsop package dimensions (sheet 2 of 2) product information symbol millimeters inches min nom max min nom max figure 3: easy bga mechanical specifications (8x10x1.2 mm) e seating plane s1 s2 e top view - ball side down bottom view - ball side up y a a1 d ball a1 corner a2 note: drawing not to scale a b c d e f g h 87 6 543 21 8 7 6 5 4 3 2 1 a b c d e f g h b ball a1 corner
datasheet jul 2011 9 order number:208034-04 p33-65nm sbc table 2: easy bga package dimensions product information symbol millimeters inches min nom max min nom max package height a - - 1.200 - - 0.0472 ball height a1 0.250 - - 0.0098 - - package body thickness a2 - 0.780 - - 0.0307 - ball (lead) width b 0.310 0.410 0.510 0.0120 0.0160 0.0200 package body width d 9.900 10.000 10.100 0.3898 0.3937 0.3976 package body length e 7.900 8.000 8.100 0.3110 0.3149 0.3189 pitch [e] - 1.000 - - 0.0394 - ball (lead) count n - 64 - - 64 - seating plane coplanarity y - - 0.100 - - 0.0039 corner to ball a1 distance along d s1 1.400 1.500 1.600 0.0551 0.0591 0.0630 corner to ball a1 distance along e s2 0.400 0.500 0.600 0.0157 0.0197 0.0236 note: daisy chain evaluation unit information is at numonyx? flash memory packaging technology http:// developer.numonyx.com/design/flash/packtech.
p33-65nm datasheet jul 2011 10 order number: 208034-04 3.0 ballouts notes: 1. a1 is the least significant address bit. 2. a23 is valid for 128-mbit densities; otherwise, it is a no connect (nc). 3. a22 is valid for 64-mbit densities and above; otherwise, it is a no connect (nc). 4. no internal connection on vcc pin 13; it may be driven or floated. for legacy designs, pin can be tied to vcc. 5. one dimple on package denotes pin 1 which will always be in the upper left corner of the package, in reference to the product mark. figure 4: 56-lead tsop pinout (64-mbit and 128-mbit densities) 56-lead tsop pinout 14 mm x 20 mm top view 1 3 4 2 5 7 8 6 9 11 12 10 13 15 16 14 17 19 20 18 21 23 24 22 25 27 28 26 56 54 53 55 52 50 49 51 48 46 45 47 44 42 41 43 40 38 37 39 36 34 33 35 32 30 29 31 a14 a13 a12 a10 a9 a11 a23 a21 vss a22 nc wp # a20 we # a19 a8 a7 a18 a6 a4 a3 a5 a2 rfu vss rfu wait dq15 dq7 a17 dq14 dq13 dq5 dq6 dq12 adv# clk dq4 rst# a16 dq3 vpp dq10 vccq dq9 dq2 dq1 dq0 vcc dq8 oe # ce# a1 vss a15 dq11
datasheet jul 2011 11 order number:208034-04 p33-65nm sbc notes: 1. a1 is the least significant address bit. 2. a23 is valid for 128-mbit densities; otherwise, it is a no connect. 3. a22 is valid for 64-mbit densities and abov e; otherwise, it is a no connect (nc). 4. one dimple on package denotes pin 1 which will always be in the upper left corner of the package, in reference to the product mark. figure 5: 64-ball easy bga ballout (64-mbit and 128-mbit densities) 1 8 234 5 67 easy bga top view- ball side down easy bga bottom view- ball side up 1 8 2 3 4 5 6 7 h g f e d c b a h g f e d c a a2 vss a9 a14 ce# a19 rfu rfu rfu vss vcc dq13 vss dq7 rfu vss a3 a7 a10 a15 a12 a20 a21 wp# a4 a5 a11 vccq rst# a16 a17 vccq rfu dq8 dq1 dq9 dq4 dq3 dq15 clk rfu oe# dq0 dq10 dq12 dq11 wait adv# we# a23 rfu dq2 dq5 vccq dq14 dq6 a1 a6 a8 a13 vpp a18 a22 vcc a23 a4 a5 a11 vccq rst# a16 a17 vccq a1 a6 a8 a13 vpp a18 a22 vcc a3 a7 a10 a15 a12 a20 a21 wp# rfu dq8 dq1 dq9 dq4 dq3 dq15 clk rfu oe # dq0 dq10 dq12 dq11 wait adv# we# rfu dq2 dq5 vccq dq14 dq6 a2 vss a9 a14 ce# a19 rfu rfu rfu vss vcc dq13 vss dq7 rfu vss b
p33-65nm datasheet jul 2011 12 order number: 208034-04 4.0 signals table 3: tsop and easy bga signal descriptions (sheet 1 of 2) symbol type name and function a[max:1] input address inputs: device address inputs. 128-mbit: a[23:1]; 64-mbit: a[22:1]. warning: the active address pins unused in design should not be left float. please tie them to vccq or vss according to sp ecific design requirements. dq[15:0] input/ output data input/outputs: inputs data and commands during write cycles; outputs data during reads of memory, status register, otp register, and read configuration register. data balls float when the ce# or oe# are deasserted. data is internally latched during writes. adv# input address valid: active low input. during synchronous read operations, addresses are latched on the rising edge of adv#, or on the next valid clk edge with adv# low, whichever occurs first. in asynchronous mode, the address is latched when adv# going high or continuously flows through if adv# is held low. warning: designs not using adv# must tie it to vss to allow addresses to flow through. ce# input chip enable: active low input. ce# low selects the associated flash memory die. when asserted, flash internal control logic, input buffers, de coders, and sense amplifiers are active. when deasserted, the associated flash die is deselected, power is reduced to standby levels, data and wait outputs are placed in high-z state. warning: all chip enables must be high when device is not in use. clk input clock: synchronizes the device with the system?s bus frequency in synchronous-read mode. during synchronous read operations, addresses are latched on the rising edge of adv#, or on the next valid clk edge with adv# low, whichever occurs first. warning: designs not using clk for synchronous read mode must tie it to vccq or vss. oe# input output enable: active low input. oe# low enables the device?s output data buffers during read cycles. oe# high places the data outputs and wait in high-z. rst# input reset: active low input. rst# resets internal automation and inhibits write operations. this provides data protection during power transitions. rst# high enables normal operation. exit from reset places the device in asynchronous read array mode. wait output wait: indicates data valid in synchronous array or non-array burst reads. rcr.10, (wt) determines its polarity when asserted. wait?s active output is v ol or v oh when ce# and oe# are v il . wait is high-z if ce# or oe# is v ih . ? in synchronous array or non-array read modes, wait indicates invalid data when asserted and valid data when deasserted. ? in asynchronous page mode, and all write modes, wait is deasserted. we# input write enable: active low input. we# controls writes to the device. address and data are latched on the rising edge of we# or ce#, whichever occurs first. wp# input write protect: active low input. wp# low enables the lock-down mechanism. blocks in lock- down cannot be unlocked with the unlock command. wp# high overrides the lock-down function enabling blocks to be erased or programmed using software commands. warning: designs not using wp# for protection could tie it to vccq or vss without additional capacitor. vpp power/ input erase and program power: a valid voltage on this pin a llows erasing or programming. memory contents cannot be altered when vpp v pplk . block erase and program at invalid vpp voltages should not be attempted. set vpp = v ppl for in-system program and erase operations. to accommodate resistor or diode drops from the system supply, the v ih level of vpp can be as low as v ppl min. vpp must remain above v ppl min to perform in-system flash modification. vpp may be 0 v during read operations. v pph can be applied to main blocks for 1000 cycles maximum and to parameter blocks for 2500 cycles. vpp can be connected to 9 v for a cumulative total not to exceed 80 hours. extended use of this pin at 9 v may reduce block cycling capability. vcc power device core power supply: core (logic) source voltage. writes to the flash array are inhibited when vcc v lko . operations at invalid vcc voltages should not be attempted. vccq power output power supply: output-driver source voltage. vss power ground: connect to system ground. do not float any vss connection.
datasheet jul 2011 13 order number:208034-04 p33-65nm sbc rfu ? reserved for future use: reserved by numonyx for future device functionality and enhancement. these should be treated in the same way as a don?t use (du) signal. du ? don?t use: do not connect to any other signal, or power supply; must be left floating. nc ? no connect: no internal connection; can be driven or floated. table 3: tsop and easy bga signal descriptions (sheet 2 of 2) symbol type name and function
p33-65nm datasheet jul 2011 14 order number: 208034-04 5.0 bus operations ce# low and rst# high enable device read operations. the device internally decodes upper address inputs to determine the accessed block. adv# low opens the internal address latches. oe# low activates the outputs and gates selected data onto the i/o bus. in asynchronous mode, the address is latched when adv# goes high or continuously flows through if adv# is held low. in synchronous mode, the address is latched by the first of either the rising adv# edge or the next valid clk edge with adv# low (we# and rst# must be v ih ; ce# must be v il ). bus cycles to/from the p33-65nm sbc device conform to standard microprocessor bus operations. table 4, ?bus operations summary? summarizes the bus operations and the logic levels that must be applied to the device control signal inputs. 5.1 read to perform a read operation, rst# and we # must be deasserted while ce# and oe# are asserted. ce# is the device-select control. when asserted, it enables the flash memory device. oe# is the data-output control. when asserted, the addressed flash memory data is driven onto the i/o bus. 5.2 write to perform a write operation, both ce# and we# are asserted while rst# and oe# are deasserted. during a write operation, address and data are latched on the rising edge of we# or ce#, whichever occurs first. table 6, ?command bus cycles? on page 18 shows the bus cycle sequence for each of the supported device commands, while table 5, ?command codes and definitions? on page 16 describes each command. see section 15.0, ?ac characteristics? on page 48 for signal-timing details. note: write operations with invalid vcc and/or vpp voltages can produce spurious results and should not be attempted. table 4: bus operations summary bus operation rst# clk adv# ce# oe# we# wait dq[15:0] notes read asynchronous v ih xl l l h deasserted output - synchronous v ih running l l l h driven output - write v ih x l l h l high-z input 1 output disable v ih x x l h h high-z high-z 2 standby v ih x x h x x high-z high-z 2 reset v il x x x x x high-z high-z 2,3,4 notes: 1. refer to the table 6, ?command bus cycles? on page 18 for valid dq[15:0] during a write operation. 2. x = don?t care (h or l). 3. rst# must be at v ss 0.2 v to meet the maximum specified power-down current. 4. recommend to set ce# and we# to v ih on 65nm device during power-on/reset to avoid invalid commands written into flash accidently.
datasheet jul 2011 15 order number:208034-04 p33-65nm sbc 5.3 output disable when oe# is deasserted, device outputs dq[15:0] are disabled and placed in a high - impedance (high-z) state, wait is also placed in high-z. 5.4 standby when ce# is deasserted the device is desele cted and placed in standby, substantially reducing power consumption. in standby, the data outputs are placed in high-z, independent of the level placed on oe#. standby current, i ccs , is the average current measured over any 5 ms time interval, 5 s after ce# is deasserted. during standby, average current is measured over the same time interval 5 s after ce# is deasserted. when the device is deselected (while ce# is deasserted) during a program or erase operation, it continues to consume active power until the program or erase operation is completed. 5.5 reset as with any automated device, it is important to assert rst# when the system is reset. when the system comes out of reset, the system processor attempts to read from the flash memory if it is the system boot device. if a cpu reset occurs with no flash memory reset, improper cpu initialization may occur because the flash memory may be providing status information rather than array data. flash memory devices from numonyx allow proper cpu initialization following a system reset through the use of the rst# input. rst# should be controlled by the same low-true reset signal that resets the system cpu. after initial power-up or reset, the device defaults to asynchronous read array mode, and the status register is set to 0x80. asserting rst# de-energizes all internal circuits, and places the output drivers in high-z. when rst# is asserted, the device shuts down the operation in progress, a process which takes a minimum amount of time to complete. when rst# has been deasserted, the device is reset to asynchronous read array state. note: if rst# is asserted during a program or erase operation, the operation is terminated and the memory contents at the aborted location (for a program) or block (for an erase) are no longer valid, because the data may have been only partially written or erased. when returning from a reset (rst# deasserted), a minimum wait is required before the initial read access outputs valid data. also, a minimum delay is required after a reset before a write cycle can be initiated. after this wake - up interval passes, normal operation is restored. see section 15.0, ?ac characteristics? on page 48 for details about signal-timing.
p33-65nm datasheet jul 2011 16 order number: 208034-04 6.0 command set 6.1 device command codes the flash command user interface (cui) provides access to device read, write, and erase operations. the cui does not occupy an addressable memory location; it is part of the internal logic which allows the flash device to be controlled. the write state machine provides the management for its internal erase and program algorithms. commands are written to the cui to control flash device operations. ta b l e 5 , ?command codes and definitions? describes all valid command codes. for operations that involve multiple command cycles, the possibility exists that the subsequent command does not get issued in the proper sequence. when this happens, the cui sets status register bits sr[5,4] to indicate a command sequence error. some applications use illegal or invalid commands (like 0x00) accidentally or intentionally with the device. an illegal or invalid command doesn't change the device output state compared with the previous operation on 130nm device. but the output will change to read status register mode on 65nm device. after an illegal or invalid command, software may attempt to read the device. if the previous state is read array mode before an illegal command, software will expect to read array data on 130nm device, such as 0xffff in an unprogrammed location. on the 65nm device, software may not get the expected array data and instead the status register is read. please refer to the legal and valid commands/spec defined in the datasheet, such as for read mode, issue 0xff to read array mode, 0x90 to read signature, 0x98 to read cfi/ otp array mode. table 5: command codes and definitions (sheet 1 of 3) mode code device mode description read 0xff read array places the device in read array mode. array data is output on dq[15:0]. 0x70 read status register places the device in read status register mode. the device enters this mode after a program or erase command is issued. sr data is output on dq[7:0]. 0x90 read device id or configuration register places device in read device identifier mode. subsequent reads output manufacturer/device codes, configuration register data, block lock status, or otp register data on dq[15:0]. 0x98 read query places the device in read query mode. subsequent reads output common flash interface information on dq[7:0]. 0x50 clear status register the wsm can only set sr error bits. the clear status register command is used to clear the sr error bits.
datasheet jul 2011 17 order number:208034-04 p33-65nm sbc write 0x40 word program setup first cycle of a 2-cycle programming command; prepares the cui for a write operation. on the next write cycle, the address and data are latched and the wsm executes the programming algorithm at the addressed location. during program operations, the device responds only to read status register and program suspend commands. ce# or oe# must be toggled to update the status register in asynchronous read. ce# or adv# must be toggled to update the sr data for synchronous non-array reads. the read array command must be issued to read array data after programming has finished. 0xe8 buffered program this command loads a variable number of words up to the buffer size of 256 words onto the program buffer. 0xd0 buffered program confirm the confirm command is issued after th e data streaming for writing into the buffer is done. this instructs the wsm to perform the buffered program algorithm, writing the data from the buffer to the flash memory array. 0x80 befp setup first cycle of a 2-cycle command; initiates the befp mode. the cui then waits for the befp confirm command, 0xd0, that initiates the befp algorithm. all other commands are ignored when befp mode begins. 0xd0 befp confirm if the previous command was befp setup (0x80), the cui latches the address and data, and prepares the device for befp mode. erase 0x20 block erase setup first cycle of a 2-cycle command; prepares the cui for a block-erase operation. the wsm performs the erase algorithm on the block addressed by the erase confirm command. if the next command is not the erase confirm (0xd0) command, the cui sets status register bits sr [5,4], and places the device in read status register mode. 0xd0 block erase confirm if the first command was block erase setup (0x20), the cui latches the address and data, and the wsm erases the addressed block. during block- erase operations, the device responds only to read status register and erase suspend commands. ce# or oe# must be toggled to update the status register in asynchronous read. ce# or adv# must be toggled to update the sr data for synchronous non-array reads. suspend 0xb0 program or erase suspend this command issued to any device address initiates a suspend of the currently-executing program or block erase operation. the status register indicates successful suspend operation by setting either sr.2 (program suspended) or sr 6 (erase suspended), along with sr.7 (ready). the wsm remains in the suspend mode regardless of control signal states (except for rst# asserted). 0xd0 suspend resume this command issued to any device address resumes the suspended program or block-erase operation. protection 0x60 block lock setup first cycle of a 2-cycle command; prepares the cui for block lock configuration changes. if the next command is not block lock (0x01), block unlock (0xd0), or block lock-down (0x2f), the cui sets sr.5 and sr.4, indicating a command sequence error. 0x01 block lock if the previous command was block lock setup (0x60), the addressed block is locked. 0xd0 unlock block if the previous command was block lock setup (0x60), the addressed block is unlocked. if the addressed block is in a lock-down state, the operation has no effect. 0x2f lock-down block if the previous command was block lock setup (0x60), the addressed block is locked down. 0xc0 protection program setup first cycle of a 2-cycle command; prepares the device for a otp register or lock register program operation. the second cycle latches the register address and data, and starts the programming algorithm to program data into the otp array. table 5: command codes and definitions (sheet 2 of 3) mode code device mode description
p33-65nm datasheet jul 2011 18 order number: 208034-04 6.2 device command bus cycles device operations are initiated by writing specific device commands to the cui. see table 6, ?command bus cycles? on page 18 . several commands are used to modify array data including word program and block erase commands. writing either command to the cui initiates a sequence of internally - timed functions that culminate in the completion of the requested task. however, the operation can be aborted by either asserting rst# or by issuing an appropriate suspend command. configuration 0x60 read configuration register setup first cycle of a 2-cycle command; prepares the cui for device read configuration. if the set read configuration register command (0x03) is not the next command, the cui sets status register bits sr.5 and sr.4, indicating a command sequence error. 0x03 read configuration register if the previous command was read configuration register setup (0x60), the cui latches the address and writes a[16:1]to the read configuration register. following a configure rcr command, subsequent read operations access array data. blank check 0xbc blank check first cycle of a 2-cycle command; initiates the blank check operation on a main block. 0xd0 blank check confirm second cycle of blank check command sequence; it latches the block address and executes blank check on the main array block. other 0xeb extended function interface this command is used in extended functi on interface. first cycle of a multiple- cycle command second cycle is a sub-op-code, the data written on third cycle is one less than the word count; the allowable value on this cycle are 0 through 511. the subsequent cycles load data words into the program buffer at a specified address until word count is achieved. table 5: command codes and definitions (sheet 3 of 3) mode code device mode description table 6: command bus cycles (sheet 1 of 2) mode command bus cycles first bus cycle second bus cycle oper addr (1) data (2) oper addr (1) data (2) read read array 1 write dna 0xff - - - read device identifier 2writedna0x90readdba + ia id read cfi 2writedna0x98readdba + cfi-acfi-d read status register 2 write dna 0x70 read dna srd clear status register 1 write dna 0x50 - - - program word program 2 write wa 0x40 write wa wd buffered program (3) > 2 write wa 0xe8 write wa n - 1 buffered enhanced factory program (befp) (4) > 2 write wa 0x80 write wa 0xd0 erase block erase 2 write ba 0x20 write ba 0xd0 suspend program/erase suspend 1writedna0xb0- - - program/erase resume 1writedna0xd0- - -
datasheet jul 2011 19 order number:208034-04 p33-65nm sbc protection lock block 2 write ba 0x60 write ba 0x01 unlock block 2 write ba 0x60 write ba 0xd0 lock-down block 2 write ba 0x60 write ba 0x2f program otp register 2 write pra 0xc0 write otp-ra otp-d program lock register 2 write lra 0xc0 write lra lrd configuration program read configuration register 2 write rcd 0x60 write rcd 0x03 others blank check 2 write ba 0xbc write ba d0 extended function interface (5) >2 write wa 0xeb write wa sub-op code notes: 1. first command cycle address should be the same as the operation?s target address. dba = device base address dna = address within the device. ia = identification code address offset. cfi-a = read cfi address offset. wa = word address of memory location to be written. ba = address within the block. otp-ra = otp register address. lra = lock register address. rcd = read configuration register data on a[16:1]. 2. id = identifier data. cfi-d = cfi data on dq[15:0]. srd = status register data. wd = word data. n = word count of data to be loaded into the write buffer. otp-d = otp register data. lrd = lock register data. 3. the second cycle of the buffered program command is the word count of the data to be loaded into the write buffer. this is followed by up to 256 words of data.then the confirm command (0xd0) is issued, triggering the array programming operation. 4. the confirm command (0xd0) is followed by the buffer data. 5. the second cycle is a sub-op-code, the data written on third cycle is n-1; 1 n 256 . the subsequent cycles load data words into the program buffer at a specified address until word count is achieved, after the data words are loaded, the final cycle is the confirm cycle 0xd0). table 6: command bus cycles (sheet 2 of 2) mode command bus cycles first bus cycle second bus cycle oper addr (1) data (2) oper addr (1) data (2)
p33-65nm datasheet jul 2011 20 order number: 208034-04 7.0 read operation the device can be in any of four read states: read array, read identifier, read status or read query. upon power-up, or after a reset, the device defaults to read array mode. to change the read state, the appropriate read command must be written to the device (see section 6.2, ?device command bus cycles? on page 18 ). the following sections describe read-mode operations in detail. the device supports two read modes: asyn chronous page mode and synchronous burst mode. asynchronous page mode is the default read mode after device power-up or a reset. the rcr must be configured to enable synchronous burst reads of the flash memory array (see section 11.1, ?read configuration register? on page 33 ). 7.1 asynchronous page-mode read following a device power-up or reset, asynchronous page mode is the default read mode and the device is set to read array mode. however, to perform array reads after any other device operation (e.g. write oper ation), the read array command must be issued in order to read from the flash memory array. to perform an asynchronous page-mode read, an address is driven onto the address bus, and ce# and adv# are asserted. we# and rst# must already have been deasserted. wait is deasserted during asynchronous page mode. adv# can be driven high to latch the address, or it must be held low throughout the read cycle. clk is not used for asynchronous page-mode reads, and is ignored. if only asynchronous reads are to be performed, clk should be tied to a valid v ih or v il level, wait signal can be floated and adv# must be tied to ground. ar ray data is driven onto dq[15:0] after an initial access time t avqv delay. (see section 15.0, ?ac characteristics? on page 48 ). in asynchronous page mode, eight data wo rds are ?sensed? simultaneously from the flash memory array and loaded into an internal page buffer. the buffer word corresponding to the initial address on the address bus is driven onto dq[15:0] after the initial access delay. the lowest four address bits determine which word of the 16-word page is output from the data buffer at any given time. 7.2 synchronous burst-mode read to perform a synchronous burst-read, an initia l address is driven onto the address bus, and ce# and adv# are asserted. we# and rs t# must already have been deasserted. adv# is asserted, and then deasserted to latch the address. alternately, adv# can remain asserted throughout the burst access, in which case the address is latched on the next valid clk edge while adv# is asserted. during synchronous array and non-array read modes, the first word is output from the data buffer on the next valid clk edge after the initial access latency delay (see section 11.1.2, ?latency count (rcr[13:11])? on page 34 ). subsequent data is output on valid clk edges following a minimum delay. however, for a synchronous non-array read, the same word of data will be output on successive clock edges until the burst length requirements are satisfied. refer to the following waveforms for more detailed information: ? figure 20, ?synchronous single-word array or non-array read timing? on page 52 ? figure 21, ?continuous burst read, showing an output delay timing? on page 53 ? figure 22, ?synchronous burst-mode four-word read timing? on page 53
datasheet jul 2011 21 order number:208034-04 p33-65nm sbc 7.3 read device identifier the read device identifier command instructs the device to output manufacturer code, device identifier code, block-lock status, otp register data, or read configuration register data (see section 6.2, ?device command bus cycles? on page 18 for details on issuing the read device identifier command). table 7, ?device identifier information? on page 21 and table 8, ?device id codes? on page 21 show the address offsets and data values for this device. 7.4 read cfi the read cfi command instructs the device to output common flash interface data when read. see section 6.1, ?device command codes? on page 16 for detail on issuing the cfi query command. section a.1, ?common flash interface? on page 60 shows cfi information and address offsets within the cfi database. table 7: device identifier information item address (1,2) data manufacturer code 0x00 0x89h device id code 0x01 id (see ta b l e 8 ) block lock configuration: bba + 0x02 lock bit: ? block is unlocked dq0 = 0b0 ? block is locked dq0 = 0b1 ? block is not locked-down dq1 = 0b0 ? block is locked-down dq1 = 0b1 read configuration register 0x05 rcr contents general purpose register (3) dba + 0x07 gpr data lock register 0 0x80 pr-lk0 64-bit factory-programmed otp register 0x81?0x84 numonyx factory otp register data 64-bit user-programmable otp register 0x85?0x88 user otp register data lock register 1 0x89 otp register lock data 128-bit user-programmable otp registers 0x8a?0x109 user otp register data notes: 1. bba = block base address. 2. dba = device base address, numonyx reserves other configuration address locations. 3. in p33-65nm sbc, the gpr is used as read out register for extended function interface command. table 8: device id codes id code type device density device identifier codes ?t (top parameter) ?b (bottom parameter) device code 64-mbit 881d 8820 128-mbit 881e 8821
p33-65nm datasheet jul 2011 22 order number: 208034-04 8.0 program operation the device supports three programming methods: word programming (40h/10h), buffered programming (e8h, d0h), and buffered enhanced factory programming (80h, d0h). the following sections describe device programming in detail. successful programming requires the addressed block to be unlocked. if the block is locked down, wp# must be deasserted and the block must be unlocked before attempting to program the block. attempting to program a locked block causes a program error (sr.4 and sr.1 set) and termination of the operation. see section 10.0, ?security? on page 29 for details on locking and unlocking blocks. 8.1 word programming word programming operations are initiated by writing the word program setup command to the device. this is followed by a second write to the device with the address and data to be programmed. the device outputs status register data when read. see figure 29, ?word program flowchart? on page 72 . vpp must be above v pplk , and within the specified v ppl min/max values. during programming, the wsm executes a sequence of internally-timed events that program the desired data bits at the addressed location, and verifies that the bits are sufficiently programmed. programming the flash memory array changes ?ones? to ?zeros?. memory array bits that are zeros can be changed to ones only by erasing the block. the status register can be examined for programming progress and errors by reading at any address. the device remains in the read status register state until another command is written to the device. status register bit sr.7 indicates the programming status while the sequence executes. commands that can be issued to the device during programming are program suspend, read status register, read device identifier, read cfi, and read array (this returns unknown data). when programming has finished, status register bit sr.4 (when set) indicates a programming failure. if sr.3 is set, the wsm could not perform the word programming operation because vpp was outside of its acceptable limits. if sr.1 is set, the word programming operation attempted to program a locked block, causing the operation to abort. before issuing a new command, the status register contents should be examined and then cleared using the clear status register command. any valid command can follow, when word programming has completed. 8.2 buffered programming the device features a 256-word buffer to enable optimum programming performance. for buffered programming, data is first writ ten to an on-chip write buffer. then the buffer data is programmed into the flash memo ry array in buffer-size increments. this can improve system programming performance significantly over non-buffered programming. (see figure 32, ?buffer program flowchart? on page 75 ). when the buffered programming setup command is issued, status register information is updated and reflects the availability of the buffer. sr.7 indicates buffer availability: if set, the buffer is available; if cleared, the buffer is not available. note: the device defaults to output sr data after the buffered programming setup command (e8h) is issued. ce# or oe# must be toggled to update status register. don?t issue the
datasheet jul 2011 23 order number:208034-04 p33-65nm sbc read sr command (70h), which would be inte rpreted by the internal state machines as buffer word count. on the next write, a word count is written to the device at the buffer address. this tells the device how many data words will be written to the buffer, up to the maximum size of the buffer. on the next write, a device start address is given along with the first data to be written to the flash memory array. subsequent writes provide additional device addresses and data. all data addresses must lie within the start address plus the word count. optimum programming performance and lower power usage are obtained by aligning the starting address at the beginning of a 256-word boundary (a[8:1] = 0x00). note: if a misaligned address range is issued during buffered programming, the program region must also be within an 256-word aligned boundary. after the last data is written to the buffer, the buffered programming confirm command must be issued to the original block address. the wsm begins to program buffer contents to the flash memory array. if a command other than the buffered programming confirm command is written to the device, a command sequence error occurs and sr[7,5,4] are set. if an error occurs while writing to the array, the device stops programming, and sr[7,4] are set, indicating a programming failure. when buffered programming has completed, additional buffer writes can be initiated by issuing another buffered programming setup command and repeating the buffered program sequence. buffered programming may be performed with vpp = v ppl or v pph (see section 13.2, ?operating conditions? on page 45 for limitations when operating the device with vpp = v pph ). if an attempt is made to program past an erase-block boundary using the buffered program command, the device aborts the operation. this generates a command sequence error, and sr[5,4] are set. if buffered programming is attempted while vpp is below v pplk , sr[4,3] are set. if any errors are detected that have set status register bits, the status register should be cleared using the clear status register command. 8.3 buffered enhanced factory programming buffered enhanced factory programing (b efp) speeds up flash programming. the enhanced programming algorithm used in befp eliminates traditional programming elements that drive up overhead in device programmer systems. (see figure 33, ?befp flowchart? on page 76 ). befp consists of three phases: setup, program/verify, and exit it uses a write buffer to spread flash program performance across 256 data words. verification occurs in the same phase as programming to accurately program the flash memory cell to the correct bit state. a single two-cycle command sequence programs the entire block of data. this enhancement eliminates three write cycles per buffer: two commands and the word count for each set of 256 data words. host programmer bus cycles fill the device?s write buffer followed by a status check. sr.0 indicates when data from the buffer has been programmed into sequential flash memory array locations. following the buffer-to-flash array programming sequence, the write state machine (wsm) increments internal addressing to automatically select the next 256-word array boundary. this aspect of befp saves host programming equipment the address-bus setup overhead.
p33-65nm datasheet jul 2011 24 order number: 208034-04 with adequate continuity testing, programming equipment can rely on the wsm?s internal verification to ensure that the device has programmed properly. this eliminates the external post-program verification and its associated overhead. 8.3.1 befp requirements and considerations note: word buffer boundaries in the array are determined by a[8: 1] (0x00 through 0xff); the alignment start point is a[8:1] = 0x00. notes: 1. some degradation in performance may occur is this limit is exceeded, but the internal algorithm continues to work properly. 2. if the internal address counter increments beyond the block?s maximum address, addressing wraps around to the beginning of the block. 3. if the number of words is less than 256, remaining locations must be filled with 0xffff. 8.3.2 befp setup phase after receiving the befp setup and confirm command sequence, status register bit sr.7 (ready) is cleared, indicating that the wsm is busy with befp algorithm startup. a delay before checking sr.7 is required to allow the wsm enough time to perform all of its setups and checks (block-lock status, vpp le vel, etc.). if an error is detected, sr.4 is set and befp operation terminates. if the block was found to be locked, sr.1 is also set. sr.3 is set if the error occurred due to an incorrect vpp level. note: reading from the device after the befp setup and confirm command sequence outputs status register data. do not issue the read status register command; it will be interpreted as data to be loaded into the buffer. table 9: befp requirements parameter/issue requirement notes case temperature t c = 30 c 10c - vcc nominal vcc - vpp driven to v pph - setup and confirm target block must be unlocked before issuing the befp setup and confirm commands. - programming the first-word address (wa0) of the block to be programmed must be held constant from the setup phase through all data stream ing into the target block, until transition to the exit phase is desired. - buffer alignment wa0 must align with the start of an array buffer boundary. 1 table 10: befp considerations parameter/issue requirement notes cycling for optimum performance, cycling must be limited below 50 erase cycles per block. 1 programming blocks befp programs one block at a time; all buffer data must fall within a single block. 2 suspend befp cannot be suspended. - programming the flash memory array programming to the flash memory array ca n occur only when the buffer is full. 3
datasheet jul 2011 25 order number:208034-04 p33-65nm sbc 8.3.3 befp program/verify phase after the befp setup phase has completed, the host programming system must check sr[7,0] to determine the availability of the write buffer for data streaming. sr.7 cleared indicates the device is busy and the befp program/verify phase is activated. sr.0 indicates the write buffer is available. two basic sequences repeat in this phase: loading of the write buffer, followed by buffer data programming to the array. for befp, th e count value for buffer loading is always the maximum buffer size of 256 words. during the buffer-loading sequence, data is stored to sequential buffer locations starting at address 0x00. programming of the buffer contents to the flash memory array starts as soon as the buffer is full. if the number of words is less than 256, the remaining buffer locations must be filled with 0xffff . caution: the buffer must be completely filled for programming to occur. supplying an address outside of the current block's range during a buffer-fill sequence causes the algorithm to exit immediately. any data previously loaded into the buffer during the fill cycle is not programmed into the array. the starting address for data entry must be buffer size aligned, if not the befp algorithm will be aborted and the program fails and (sr.4) flag will be set. data words from the write buffer are directed to sequential memory locations in the flash memory array; programming continues from where the previous buffer sequence ended. the host programming system must poll sr.0 to determine when the buffer program sequence completes. sr.0 cleared indicates that all buffer data has been transferred to the flash array; sr.0 set indicates that the buffer is not available yet for the next fill cycle. the host system may check full status for errors at any time, but it is only necessary on a block basis after befp exit. after the buffer fill cycle, no write cycles should be issued to the device until sr.0 = 0 and the device is ready for the next buffer fill. note: any spurious writes are ignored after a buffer fill operation and when internal program is proceeding. the host programming system continues the befp algorithm by providing the next group of data words to be written to the buffer. alternatively, it can terminate this phase by changing the block address to one outside of the current block?s range. the program/verify phase concludes when the programmer writes to a different block address; data supplied must be 0xffff. upon program/verify phase completion, the device enters the befp exit phase. 8.3.4 befp exit phase when sr.7 is set, the device has returned to normal operating conditions. a full status check should be performed at this time to ensure the entire block programmed successfully. when exiting the befp algorithm with a block address change, the read mode will not change. after befp exit, any valid command can be issued to the device. 8.4 program suspend issuing the program suspend command while programming suspends the programming operation. this allows data to be accessed from the device other than the one being programmed. the program suspend command can be issued to any device address. a program operation can be suspended to perform reads only. additionally, a
p33-65nm datasheet jul 2011 26 order number: 208034-04 program operation that is running during an erase suspend can be suspended to perform a read operation (see figure 30, ?program suspend/resume flowchart? on page 73 ). when a programming operation is executing, issuing the program suspend command requests the wsm to suspend the programming algorithm at predetermined points. the device continues to output status register data after the program suspend command is issued. programming is suspended when status register bits sr[7,2] are set. suspend latency is specified in section 15.5, ?program and erase characteristics? on page 58 . to read data from the device, the read ar ray command must be issued. read array, read status register, read device identifier, read cfi, and program resume are valid commands during a program suspend. during a program suspend, deasserting ce# places the device in standby, reducing active current. vpp must remain at its programming level, and wp# must remain unchanged while in program suspend. if rst# is asserted, the device is reset. 8.5 program resume the resume command instructs the device to continue programming, and automatically clears status register bits sr[7,2]. this command can be written to any address. if error bits are set, the status register should be cleared before issuing the next instruction. rst# must remain deasserted (see figure 30, ?program suspend/ resume flowchart? on page 73 ). 8.6 program protection when vpp = v il , absolute hardware write protection is provided for all device blocks. if vpp is at or below v pplk , programming operations halt and sr.3 is set indicating a vpp- level error. block lock registers are not affected by the voltage level on vpp; they may still be programmed and read, even if vpp is less than v pplk . figure 6: example vpp supply connections ? factory programming with v pp = v pph ? complete write/erase protection when v pp v pplk vcc vpp vcc vpp ? low voltage and factory programming ? low-voltage programming only ? logic control of device protection vcc vpp ? low voltage programming only ? full device protection unavailable vcc vpp 10k v pp v cc v cc prot # v cc v pp =v pph v cc
datasheet jul 2011 27 order number:208034-04 p33-65nm sbc 9.0 erase operation flash erasing is performed on a block basis. an entire block is erased each time an erase command sequence is issued, and only one block is erased at a time. when a block is erased, all bits within that block read as logical ones. the following sections describe block erase operations in detail. 9.1 block erase block erase operations are initiated by writing the block erase setup command to the address of the block to be erased (see section 6.2, ?device command bus cycles? on page 18 ). next, the block erase confirm command is written to the address of the block to be erased. if the device is placed in standby (ce# deasserted) during an erase operation, the device completes the erase operation before entering standby. vpp must be above v pplk and the block must be unlocked (see figure 34, ?block erase flowchart? on page 77 ). during a block erase, the wsm executes a sequence of internally-timed events that conditions, erases, and verifies all bits within the block. erasing the flash memory array changes ?zeros? to ?ones?. memory array bits that are ones can be changed to zeros only by programming the block. the status register can be examined for block erase progress and errors by reading any address. the device remains in the read status register state until another command is written. sr.0 indicates whether the addressed block is erasing. status register bit sr.7 is set upon erase completion. status register bit sr.7 indicates block erase status while the sequence executes. when the erase operation has finished, status register bit sr.5 indicates an erase failure if set. sr.3 set would indicate that the wsm could not perform the erase operation because vpp was outside of its acceptable limits. sr.1 set indicates that the erase operation attempted to erase a locked block, causing the operation to abort. before issuing a new command, the status register contents should be examined and then cleared using the clear status register command. any valid command can follow once the block erase operation has completed. the block erase operation is aborted by performing a reset or powering down the device. in this case, data integrity cannot be ensured, and it is recommended to erase again the blocks aborted. 9.2 blank check the blank check operation determines whether a specified main block is blank (i.e. completely erased). without blank check, block erase would be the only other way to ensure a block is completely erased. so blank check can be used to determine whether or not a prior erase operation was successful; this includes erase operations that may have been interrupted by power loss. blank check can apply to only one block at a time, and no operations other than status register reads are allowed during blank check (e.g. reading array data, program, erase etc). suspend and resume operations are not supported during blank check, nor is blank check supported during any suspended operations. blank check operations are initiated by writing the blank check setup command to the block address. next, the check confirm command is issued along with the same block address. when a successful command sequence is entered, the device automatically enters the read status state. the wsm then reads the entire specified block, and determines whether any bit in the block is programmed or over-erased.
p33-65nm datasheet jul 2011 28 order number: 208034-04 the status register can be examined for blank check progress and errors by reading any address within the block being accessed. during a blank check operation, the status register indicates a busy status (sr.7 = 0). upon completion, the status register indicates a ready status (sr.7 = 1). the status register should be checked for any errors, and then cleared. if the blank check operation fails, which means the block is not completely erased, the status register bit sr.5 will be set (?1?). ce# or oe# toggle (during polling) updates the status register. after examining the status register, it should be cleared by the clear status register command before issuing a new command. the device remains in status register mode until another command is written to the device. any command can follow once the blank check command is complete. 9.3 erase suspend issuing the erase suspend command while erasing suspends the block erase operation. this allows data to be accessed from memory locations other than the one being erased. the erase suspend command can be issued to any device address. a block erase operation can be suspended to perform a word or buffer program operation, or a read operation within any block except the block that is erase suspended (see figure 31, ?erase suspend/resume flowchart? on page 74 ). when a block erase operation is executing, issuing the erase suspend command requests the wsm to suspend the erase algorithm at predetermined points. the device continues to output status register data after the erase suspend command is issued. block erase is suspended when status register bits sr[7,6] are set. suspend latency is specified in section 15.5, ?program and erase characteristics? on page 58 . to read data from the device (other than an erase-suspended block), the read array command must be issued. during erase su spend, a program command can be issued to any block other than the erase-suspended block. block erase cannot resume until program operations initiated during erase suspend complete. read array, read status register, read device identifier, read cfi, and erase resume are valid commands during erase suspend. additionally, clear status register, program, program suspend, block lock, block unlock, and block lock -down are valid commands during erase suspend. during an erase suspend, deasserting ce# places the device in standby, reducing active current. vpp must remain at a valid level, and wp# must remain unchanged while in erase suspend. if rst# is asserted, the device is reset. 9.4 erase resume the erase resume command instructs the device to continue erasing, and automatically clears sr[7,6]. this command can be written to any address. if status register error bits are set, the status register should be cleared before issuing the next instruction. rst# must remain deasserted. 9.5 erase protection when vpp = v il , absolute hardware erase protection is provided for all device blocks. if vpp is at or below v pplk , erase operations halt and sr.3 is set indicating a vpp-level error.
datasheet jul 2011 29 order number:208034-04 p33-65nm sbc 10.0 security the device features security modes used to protect the information stored in the flash memory array. the following sections describe each security mode in detail. 10.1 block locking individual instant block locking is used to protect user code and/or data within the flash memory array. all blocks power up in a locked state to protect array data from being altered during power transitions. any block can be locked or unlocked with no latency. locked blocks cannot be programmed or erased; they can only be read. software-controlled security is implemented using the block lock and block unlock commands. hardware-controlled security can be implemented using the block lock- down command along with asserting wp#. also, vpp data security can be used to inhibit program and erase operations (see section 8.6, ?program protection? on page 26 and section 9.5, ?erase protection? on page 28 ). the p33-65nm sbc device also offers four pre-defined areas in the main array that can be configured as one-time programmable (otp) for the highest level of security. these include the four 32 kb parameter blocks together as one and the three adjacent 128 kb main blocks. this is available for top or bottom parameter devices. 10.1.1 lock block to lock a block, issue the lock block setup command. the next command must be the lock block command issued to the desired block?s address (see section 6.2, ?device command bus cycles? on page 18 and figure 35, ?block lock operations flowchart? on page 78 ). if the set read configuration register command is issued after the block lock setup command, the device configures the rcr instead. block lock and unlock operations are not affected by the voltage level on vpp. the block lock bits may be modified and/or read even if vpp is at or below v pplk . 10.1.2 unlock block the unlock block command is used to unlock blocks (see section 6.2, ?device command bus cycles? on page 18 ). unlocked blocks can be read, programmed, and erased. unlocked blocks return to a locked state when the device is reset or powered down. if a block is in a lock-down state, wp# must be deasserted before it can be unlocked (see figure 7, ?block locking state diagram? on page 30 ). 10.1.3 lock-down block a locked or unlocked block can be locked-down by writing the lock-down block command sequence (see section 6.2, ?device command bus cycles? on page 18 ). blocks in a lock-down state cannot be programmed or erased; they can only be read. however, unlike locked blocks, their locked state cannot be changed by software commands alone. a locked-down block can only be unlocked by issuing the unlock block command with wp# deasserted. to return an unlocked block to locked-down state, a lock-down command must be issued prior to changing wp# to v il . locked- down blocks revert to the locked state upon reset or power up the device (see figure 7, ?block locking state diagram? on page 30 ).
p33-65nm datasheet jul 2011 30 order number: 208034-04 10.1.4 block lock status the read device identifier command is used to determine a block?s lock status (see section 7.3, ?read device identifier? on page 21 ). data bits dq[1:0] display the addressed block?s lock status; dq0 is the a ddressed block?s lock bit, while dq1 is the addressed block?s lock-down bit. note: lk: lock setup command, 60h; lk/d0h: unlock command; lk/01h: lock command; lk/2fh: lock-down command. 10.1.5 block locking during suspend block lock and unlock changes can be perfor med during an erase suspend. to change block locking during an erase operation, first issue the erase suspend command. monitor the status register until sr.7 and sr.6 are set, indicating the device is suspended and ready to accept another command. next, write the desired lock command sequence to a block, which changes the lock state of that block. after completing block lock or unlock operations, resume the erase operation using the erase resume command. note: a lock block setup command followed by any command other than lock block, unlock block, or lock-down block produces a command sequence error and set status register bits sr.4 and sr.5. if a command sequence error occurs during an erase suspend, sr.4 and sr.5 remains set, even after the erase operation is resumed. unless the status register is cleared using the clear status register command before resuming the erase operation, possible erase errors may be masked by the command sequence error. figure 7: block locking state diagram [000] [001] [011] [111] [101] [110] [100] lk/ d0h lk/ 01h lk/ 2fh l k / 2 f h lk/ d0h lk/ 01h or 2fh lk/ d0h lk/ 01h lk/ 2fh lk/ 2fh pgm/erase allow ed pgm/erase prevented wp# = v il = 0 wp# = v ih = 1 power-up/ r eset d efault power-up/ r eset d efau lt locked-down locked-down is disabled by wp# = v ih v irtu al lo ck- down any lock com m ands w p# toggle w p # t o g g l e [010]
datasheet jul 2011 31 order number:208034-04 p33-65nm sbc if a block is locked or locked-down during an erase suspend of the same block, the lock status bits change immediately. however, the erase operation completes when it is resumed. block lock operations cannot occur during a program suspend. see appendix a, ?write state machine? on page 81 , which shows valid commands during an erase suspend. 10.2 selectable otp blocks blocks from the main array may be optionally configured as otp. ask your local numonyx representative for details about any of these selectable otp implementations. 10.3 password access password access is a security enhancement offered on the p33-65nm device. this feature protects information stored in main-array memory blocks by preventing content alteration or reads until a valid 64-bit password is received. password access may be combined with non-volatile protection and/or volatile protection to create a multi- tiered solution. please contact your numonyx sales for further details concerning password access.
p33-65nm datasheet jul 2011 32 order number: 208034-04 11.0 status register to read the status register, issue the read status register command at any address. status register information is available to which the read status register, word program, or block erase command was issued. srd is automatically made available following a word program, block erase, or block lock command sequence. reads from the device after any of these command sequences outputs the device?s status until another valid command is written (e.g. the read array command). the status register is read using single asynchronous-mode or synchronous burst mode reads. srd is output on dq[7:0], while 0x00 is output on dq[15:8]. in asynchronous mode the falling edge of oe#, or ce# (whichever occurs first) updates and latches the status register contents. however, when reading the status register in synchronous burst mode, ce# or adv# must be toggled to update srd. the device ready status bit (sr.7) provides overall status of the device. sr[6:1] present status and error information about the program, erase, suspend, vpp, and block-locked operations. table 11: status register description status register (sr) default value = 0x80 device ready status erase suspend status 1 1. always clear the status register before resuming erase operations afer an erase suspend command; this prevents ambiguity in status register information. for example, if a command sequ ence error occurs during an erase suspend state, the status register contains the command sequence error status (sr[7,5,4] set). when the erase operation resumes and finishes, possible errors during the erase operation cannot be deteted via the stauts register because it contains the previous error status. erase/blank check status program status vpp status program suspend status block-locked status befp write status drs ess es ps vpps pss bls bws 76543210 bit name description 7 device ready status 0 = device is busy; program or erase cycle in progress; sr.0 valid. 1 = device is ready; sr[6:1] are valid. 6 erase suspend status 0 = erase suspend not in effect. 1 = erase suspend in effect. 5 erase/blank check status command sequence error sr.5 sr.4 description 4 program status 0 0 1 1 0 1 0 1 program or erase operation successful. program error -operation aborted. erase or blank check error - operation aborted. command sequence error - command aborted. 3 vpp status 0 = vpp within acceptable limits du ring program or erase operation. 1 = vpp < v pplk during program or erase operation. 2 program suspend status 0 = program suspend not in effect. 1 = program suspend in effect. 1block-locked status 0 = block not locked during program or erase. 1 = block locked during program or erase; operation aborted. 0befp write status 2 2. befp mode is only valid in array. after buffered enhanced factory programming (befp) data is loaded into the buffer: 0 = befp complete. 1 = befp in-progress.
datasheet jul 2011 33 order number:208034-04 p33-65nm sbc 11.0.1 clear status register the clear status register command clears the status register. it functions independent of vpp. the wsm sets and clears sr[7,6,2], but it sets bits sr[5:3,1] without clearing them. the status register should be cleared before starting a command sequence to avoid any ambiguity. a device reset also clears the status register. 11.1 read configuration register the rcr is used to select the read mode (synchronous or asynchronous), and it defines the synchronous burst characteristics of the device. to modify rcr settings, use the configure read configuration register command (see section 6.2, ?device command bus cycles? on page 18 ). rcr contents can be examined using the read device identifier command, and then reading from offset 0x05 (see section 7.3, ?read device identifier? on page 21 ). the rcr is shown in ta b l e 1 2 . the following sections describe each rcr bit. table 12: read configuration register description (sheet 1 of 2) read configuration register (rcr) read mode res latency count wait polarity data output config wait delay burst seq clk edge res res burst wrap burst length rm r lc[3:0] wp doc wd bs ce r r bw bl[2:0] 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 bit name description 15 read mode (rm) 0 = synchronous burst-mode read 1 = asynchronous page-mode read (default) 14 reserved (r) set to 0. this bit cannot be altered by customer. 13:11 latency count (lc[2:0]) 000 =code 0 reserved 001 =code 1 reserved 010 =code 2 011 =code 3 100 =code 4 101 =code 5 110 =code 6 111 =code 7(default) 10 wait polarity (wp) 0 =wait signal is active low 1 =wait signal is active high (default) 9 data output configuration (doc) 0 =data held for a 1-clock data cycle 1 =data held for a 2-clock data cycle (default) 8 wait delay (wd) 0 =wait deasserted with valid data 1 =wait deasserted one data cycle before valid data (default) 7 burst sequence (bs) 0 =reserved 1 =linear (default) 6 clock edge (ce) 0 = falling edge 1 = rising edge (default)
p33-65nm datasheet jul 2011 34 order number: 208034-04 11.1.1 read mode (rcr.15) the read mode (rm) bit selects synchronous burst-mode or asynchronous page-mode operation for the device. when the rm bit is set, asynchronous page mode is selected (default). when rm is cleared, synchronous burst mode is selected. 11.1.2 latency count (rcr[13:11]) the latency count (lc) bits tell the device how many clock cycles must elapse from the rising edge of adv# (or from the first valid clock edge after adv# is asserted) until the first valid data word is driven onto dq[15:0]. the input clock frequency is used to determine this value and figure 8 shows the data output latency for the different settings of lc. the maximum latency count for p33 would be code 4 based on the max clock frequency specification of 52 mhz, and there will be zero wait states when bursting within the word line. please also refer to section 11.1.3, ?end of word line (eowl) considerations? on page 36 for more information on eowl. refer to table 13, ?lc and frequency support? on page 35 for latency code settings. 5:4 reserved (r) set to 0. this bit cannot be altered by customer. 3 burst wrap (bw) 0 =wrap; burst accesses wrap within burst length set by bl[2:0] 1 =no wrap; burst accesses do not wrap within burst length (default) 2:0 burst length (bl[2:0]) 001 =4-word burst 010 =8-word burst 011 =16-word burst 111 =continuous-word burst (default) (other bit settings are reserved) table 12: read configuration register description (sheet 2 of 2)
datasheet jul 2011 35 order number:208034-04 p33-65nm sbc figure 8: first-access latency count table 13: lc and frequency support latency count settings frequency support (mhz) 3 40 4 52 code 1 (reserved code 6 code 5 code 4 code 3 code 2 code 0 (reserved) code 7 vali d address valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output valid output address [a] adv# [v] dq 15-0 [d/q] clk [c] dq 15-0 [d/q] dq 15-0 [d/q] dq 15-0 [d/q] dq 15-0 [d/q] dq 15-0 [d/q] dq 15-0 [d/q] dq 15-0 [d/q]
p33-65nm datasheet jul 2011 36 order number: 208034-04 11.1.3 end of word line (eowl) considerations end of wordline (eowl) wait states can result when the starting address of the burst operation is not aligned to an 8-word boundary; that is, a[3:1] of start address does not equal 0x0. figure 10, ?end of wordline timing diagram? on page 36 illustrates the end of wordline wait state(s), which occur after the first 8-word boundary is reached. the number of data words and the number of wait states is summarized in table 14, ?end of wordline data and wait state comparison? on page 37 for both p33-130nm and p33-65nm sbc devices. figure 9: example latency count setting using code 3 clk ce# adv# a[max:0] d[15:0] t data code 3 address data 012 34 r103 high-z a[max:1] figure 10: end of wordline timing diagram a[max:1] adv# oe# wait dq[15:0] data data data eowl clk latency count address
datasheet jul 2011 37 order number:208034-04 p33-65nm sbc table 14: end of wordline data and wait state comparison 11.1.4 wait polarity (rcr.10) the wait polarity bit (wp), rcr.10 determines the asserted level (v oh or v ol ) of wait. when wp is set, wait is asserted high. when wp is cleared, wait is asserted low (default). wait changes state on valid cl ock edges during active bus cycles (ce# asserted, oe# asserted, rst# deasserted). 11.1.5 wait signal function the wait signal indicates data valid when the device is operating in synchronous mode (rcr.15=0). the wait signal is only ?deasserted? when data is valid on the bus. when the device is operating in synchronous non-array read mode, such as read status, read id, or read query. the wait signal is also ?deasserted? when data is valid on the bus. wait behavior during synchronous non-array reads at the end of word line works correctly only on the first data access. when the device is operating in asynchronous page mode, asynchronous single word read mode, and all write operations, wait is set to a deasserted state as determined by rcr.10. see figure 18, ?asynchronous single-word read (adv# latch)? on page 51 , and figure 19, ?asynchronous page-mode read timing? on page 52 . latency count p33-130nm p33-65nm data states wait states data states wait states 1 not supported not supported not supported not supported 2 4 0 to 1 8 0 to 1 3 4 0 to 2 8 0 to 2 4 4 0 to 3 8 0 to 3 5 4 0 to 4 8 0 to 4 6 4 0 to 5 8 0 to 5 7 4 0 to 6 8 0 to 6
p33-65nm datasheet jul 2011 38 order number: 208034-04 11.1.6 data output configuration (rcr.9) the data output configuration (doc) bit, rcr.9 determines whether a data word remains valid on the data bus for one or two clock cycles. this period of time is called the ?data cycle?. when doc is set, output data is held for two clocks (default). when doc is cleared, output data is held for one clock (see figure 11, ?data hold timing? on page 38 ). the processor?s data setup time and the flash memory?s clock-to-data output delay should be considered when determining whether to hold output data for one or two clocks. a method for determining the data hold configuration is shown below: to set the device at one clock data hold for subsequent reads, the following condition must be satisfied: t chqv (ns) + t data (ns) one clk period (ns) t data = data set up to clock (defined by cpu) for example, with a clock frequency of 40 mhz, the clock period is 25 ns. assuming t chqv = 20 ns and t data = 4 ns. applying these values to the formula above: 20 ns + 4 ns 25 ns the equation is satisfied and data will be av ailable at every clock period with data hold setting at one clock. if t chqv (ns) + t data (ns) > one clk period (ns), data hold setting of 2 clock periods must be used. table 15: wait functionality table condition wait notes ce# = ?1?, oe# = ?x? or ce# = ?0?, oe# = ?1? high-z 1 ce# =?0?, oe# = ?0? active 1 synchronous array reads active 1 synchronous non-array reads active 1 all asynchronous reads deasserted 1 all writes high-z 1,2 notes: 1. active: wait is asserted until data becomes valid, then deasserts. 2. when oe# = v ih during writes, wait = high-z. figure 11: data hold timing valid output valid output valid output valid output valid output clk [c] d[15:0] [q] d[15:0] [q] 2 clk data hold 1 clk data hold
datasheet jul 2011 39 order number:208034-04 p33-65nm sbc 11.1.7 wait delay (rcr.8) the wait delay (wd) bit controls the wait assertion-delay behavior during synchronous burst reads. wait can be asserted either during or one data cycle before valid data is output on dq[15:0]. when wd is set, wait is deasserted one data cycle before valid data (default). when wd is cleared, wait is deasserted during valid data. 11.1.8 burst sequence (rcr.7) the burst sequence (bs) bit selects linear-bur st sequence (default). only linear-burst sequence is supported. ta b l e 1 6 shows the synchronous burst sequence for all burst lengths, as well as the effect of the burst wrap (bw) setting. table 16: burst sequence word ordering start addr. (dec) burst wrap (rcr.3) burst addressing sequence (dec) 4-word burst (bl[2:0] = 0b001) 8-word burst (bl[2:0] = 0b010) 16-word burst (bl[2:0] = 0b011) continuous burst (bl[2:0] = 0b111) 0 0 0-1-2-3 0-1-2-3-4-5-6-7 0-1-2-3-4?14-15 0-1-2-3-4-5-6-? 1 0 1-2-3-0 1-2-3-4-5-6-7-0 1-2-3-4-5?15-0 1-2-3-4-5-6-7-? 2 0 2-3-0-1 2-3-4-5-6-7-0-1 2-3-4-5-6?15-0-1 2-3-4-5-6-7-8-? 3 0 3-0-1-2 3-4-5-6-7-0-1-2 3-4-5-6-7?15-0-1-2 3-4-5-6-7-8-9-? 40 4-5-6-7-0-1-2-3 4-5-6-7-8?15-0-1-2-3 4-5-6-7-8-9-10? 50 5-6-7-0-1-2-3-4 5-6-7-8-9?15-0-1-2-3- 4 5-6-7-8-9-10-11? 60 6-7-0-1-2-3-4-5 6-7-8-9-10?15-0-1-2- 3-4-5 6-7-8-9-10-11-12-? 70 7-0-1-2-3-4-5-6 7-8-9-10?15-0-1-2-3- 4-5-6 7-8-9-10-11-12-13? ? ? ? ? ? ? 14 0 14-15-0-1-2?12-13 14-15-16-17-18-19-20- ? 15 0 15-0-1-2-3?13-14 15-16-17-18-19-20-21- ? ? ? ? ? ? ? 0 1 0-1-2-3 0-1-2-3-4-5-6-7 0-1-2-3-4?14-15 0-1-2-3-4-5-6-? 1 1 1-2-3-4 1-2-3-4-5-6-7-8 1-2-3-4-5?15-16 1-2-3-4-5-6-7-? 2 1 2-3-4-5 2-3-4-5-6-7-8-9 2-3-4-5-6?16-17 2-3-4-5-6-7-8-? 3 1 3-4-5-6 3-4-5-6-7-8-9-10 3-4-5-6-7?17-18 3-4-5-6-7-8-9-? 41 4-5-6-7-8-9-10-11 4-5-6-7-8?18-19 4-5-6-7-8-9-10? 51 5-6-7-8-9-10-11-12 5-6-7-8-9?19-20 5-6-7-8-9-10-11? 61 6-7-8-9-10-11-12-13 6-7-8-9-10?20-21 6-7-8-9-10-11-12-? 71 7-8-9-10-11-12-13-14 7-8-9-10-11?21-22 7-8-9-10-11-12-13? ? ? ? ? ? ? 14 1 14-15-16-17-18?28-29 14-15-16-17-18-19-20- ? 15 1 15-16-17-18-19?29-30 15-16-17-18-19-20-21- ?
p33-65nm datasheet jul 2011 40 order number: 208034-04 11.1.9 clock edge (rcr.6) the clock edge (ce) bit selects either a rising (default) or falling clock edge for clk. this clock edge is used at the start of a burst cycle, to output synchronous data, and to assert/deassert wait. 11.1.10 burst wrap (rcr.3) the burst wrap (bw) bit determines whether 4, 8, or 16-word burst length accesses wrap within the selected word-length boun daries or cross word-length boundaries. when bw is set, burst wrapping does not occur (default). when bw is cleared, burst wrapping occurs. 11.1.11 burst length (rcr[2:0]) the burst length bits (bl[2:0]) selects the linear burst length for all synchronous burst reads of the flash memory array. the burst lengths are 4-word, 8-word, 16-word, and continuous word. continuous burst accesses are linear only, and do not wrap within any word length boundaries (see table 16, ?burst sequence word ordering? on page 39 ). when a burst cycle begins, the device outputs synchronous burst data until it reaches the end of the ?burstable? address space. 11.2 one-time programmable (otp) registers the device contains 17 otp registers that can be used to implement system security measures and/or device identification. each otp register can be individually locked. the first 128-bit otp register is comprised of two 64-bit (8-word) segments. the lower 64-bit segment is pre-programmed at the numonyx factory with a unique 64-bit number. the other 64-bit segment, as well as the other sixteen 128-bit otp registers, are blank. users can program these registers as needed. once programmed, users can then lock the otp register(s) to prevent additional bit programming (see figure 12, ?otp register map? on page 41 ). the otp registers contain otp bits; when programmed, pr bits cannot be erased. each otp register can be accessed multiple times to program individual bits, as long as the register remains unlocked. each otp register has an associated lock register bit. when a lock register bit is programmed, the associated otp register can only be read; it can no longer be programmed. additionally, because the lock register bits themselves are otp, when programmed, lock register bits cannot be erased. therefore, when a otp register is locked, it cannot be unlocked.
datasheet jul 2011 41 order number:208034-04 p33-65nm sbc . 11.2.1 reading the otp registers the otp registers can be read from otp-ra address. to read the otp register, first issue the read device identifier command at otp-ra address to place the device in the read device identifier state (see section 6.2, ?device command bus cycles? on page 18 ). next, perform a read operation using the address offset corresponding to the register to be read. table 7, ?device identifier information? on page 21 shows the address offsets of the otp registers and lock registers. pr data is read 16 bits at a time. 11.2.2 programming the otp registers to program any of the otp registers, first issue the program otp register command at the parameter?s base address plus the offset to the desired otp register (see section 6.2, ?device command bus cycles? on page 18 ). next, write the desired otp register data to the same otp register address (see figure 12, ?otp register map? on page 41 ). figure 12: otp register map 0x89 lock register 1 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 0x102 0x109 0x8a 0x91 128-bit otp register 16 (user-programmable) 128-bit otp register 1 (user-programmable) 0x88 0x85 64-bit segment (user-programmable) 0x84 0x81 0x80 lock register 0 64-bit segment (factory-programmed) 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 128-bit otp register 0
p33-65nm datasheet jul 2011 42 order number: 208034-04 the device programs the 64-bit and 128-bit user-programmable otp register data 16 bits at a time (see figure 36, ?otp register programming flowchart? on page 79 ). issuing the program otp register command outside of the otp register?s address space causes a program error (sr.4 set). attempting to program a locked otp register causes a program error (sr.4 set) and a lock error (sr.1 set). note: when programming the otp bits in the otp registers for a top parameter device, the following upper address bits must also be driven properly: a[max:17] driven high (v ih ). 11.2.3 locking the otp registers each otp register can be locked by programming its respective lock bit in the lock register. to lock a otp register, program the corresponding bit in the lock register by issuing the program lock register command, followed by the desired lock register data (see section 6.2, ?device command bus cycles? on page 18 ). the physical addresses of the lock registers are 0x80 for register 0 and 0x89 for register 1. these addresses are used when programming the lock registers (see table 7, ?device identifier information? on page 21 ). bit 0 of lock register 0 is already programmed during the manufacturing process at the ?factory?, locking the lower, pre-programmed 64-bit region of the first 128-bit otp register containing the unique identification number of the device. bit 1 of lock register 0 can be programmed by the user to lock the user-programmable, 64-bit region of the first 128-bit otp register. when programming bit 1 of lock register 0, all other bits need to be left as ?1? such that the data programmed is 0xfffd. lock register 1 controls the locking of the upper sixteen 128-bit otp registers. each of the 16 bits of lock register 1 correspond to each of the upper sixteen 128-bit otp registers. programming a bit in lock register 1 locks the corresponding 128-bit otp register. caution: after being locked, the otp re gisters cannot be unlocked.
datasheet jul 2011 43 order number:208034-04 p33-65nm sbc 12.0 power and reset specifications 12.1 power-up and power-down power supply sequencing is not required if vpp is connected to vcc or vccq. otherwise vcc and vccq should attain their minimum operating voltage before applying vpp. power supply transitions should only occur when rst# is low. this protects the device from accidental programming or erasure during power transitions. 12.2 reset specifications asserting rst# during a system reset is important with automated program/erase devices because systems typically expect to read from flash memory when coming out of reset. if a cpu reset occurs without a fl ash memory reset, proper cpu initialization may not occur. this is because the flash memory may be providing status information, instead of array data as expected. connect rst# to the same active low reset signal used for cpu initialization. also, because the device is disabled when rst# is asserted, it ignores its control inputs during power-up/down. invalid bus conditions are masked, providing a level of memory protection. table 17: power and reset num symbol parameter min max unit notes p1 t plph rst# pulse width low 100 - ns 1,2,3,4 p2 t plrh rst# low to device reset during erase - 25 s 1,3,4,7 rst# low to device reset during program - 25 1,3,4,7 p3 t vccph vcc power valid to rst# de-assertion (high) 60 - 1,4,5,6 notes: 1. these specifications are valid for all device versions (packages and speeds). 2. the device may reset if t plph is < t plph min, but this is not guaranteed. 3. not applicable if rst# is tied to vcc. 4. sampled, but not 100% tested. 5. when rst# is tied to the vcc supply, device will not be ready until t vccph after vcc v ccmin . 6. when rst# is tied to the vccq supply, device will not be ready until t vccph after vcc v ccmin . 7. reset completes within t plph if rst# is asserted while no erase or program operation is executing.
p33-65nm datasheet jul 2011 44 order number: 208034-04 12.3 power supply decoupling flash memory devices require careful power supply de-coupling. three basic power supply current considerations are: 1) standby current levels; 2) active current levels; and 3) transient peaks produced when ce# and oe# are asserted and deasserted. when the device is accessed, many internal conditions change. circuits within the device enable charge-pumps, and internal logic states change at high speed. all of these internal activities produce transient signals. transient current magnitudes depend on the device outputs? capacitive and inductive loading. two-line control and correct de-coupling capacitor selection suppress transient voltage peaks. because numonyx flash memory devices draw their power from vcc, vpp, and vccq, each power connection should have a 0.1 f ceramic capacitor to ground. high- frequency, inherently low-inductance capacitors should be placed as close as possible to package leads. additionally, for every eight devices used in the system, a 4.7 f electrolytic capacitor should be placed between power and ground close to the devices. the bulk capacitor is meant to overcome voltage droop caused by pcb trace inductance. figure 13: reset operation waveforms ( a) reset during read mode (b) reset during program or block erase p1 p2 (c) reset during program or block erase p1 p2 v ih v il v ih v il v ih v il rst# [p] rst# [p] rst# [p] abort complete abort complete v cc 0v v cc (d) vcc power-up to rst# high p1 r5 p2 p3 p2 r5 r5
datasheet jul 2011 45 order number:208034-04 p33-65nm sbc 13.0 maximum ratings and operating conditions 13.1 absolute maximum ratings warning: stressing the device beyond the absolute maximum ratings may cause permanent damage. these are stress ratings only. 13.2 operating conditions note: operation beyond the operating conditions is not recommended and extended exposure beyond the operating conditions may affect device reliability. table 18: absolute maximum ratings parameter maximum rating notes temperature under bias ?40 c to +85 c - storage temperature ?65 c to +125 c - voltage on any input/output signal (except vcc, vpp and vccq) ?2.0 v to +5.6 v 1 vpp voltage ?2.0 v to +11.5 v 1,2 vcc voltage ?2.0 v to +5.6 v 1 vccq voltage ?2.0 v to +5.6 v 1 output short circuit current 100 ma 3 notes: 1. voltages shown are specified with respect to v ss . during infrequent non-periodic transitions, the level may undershoot to ?2.0 v for periods less than 20 ns or overshoot to vcc + 2.0 v or vccq + 2.0 v for periods less than 20 ns. 2. program/erase voltage is typically 2.3 v ~ 3.6 v. 9.0 v ca n be applied for 80 hours maximum total. 9.0 v program/erase voltage may reduce block cycling capability. 3. output shorted for no more than one second. no more than one output shorted at a time. table 19: operating conditions symbol parameter min max units notes t c operating temperature ?40 +85 c 1 vcc vcc supply voltage 2.3 3.6 v - vccq i/o supply voltage cmos inputs 2.3 3.6 - ttl inputs 2.4 3.6 v ppl v pp voltage supply (logic level) 1.5 3.6 2 v pph buffered enhanced factory programming v pp 8.5 9.5 t pph maximum v pp hours vpp = v pph -80hours block erase cycles main and parameter blocks vpp = v ppl 100,000 - cycles main blocks vpp = v pph - 1000 parameter blocks vpp = v pph - 2500 notes: 1. t c = case temperature. 2. in typical operation vpp program voltage is v ppl .
p33-65nm datasheet jul 2011 46 order number: 208034-04 14.0 electrical specifications 14.1 dc current characteristics table 20: dc current characteristics (sheet 1 of 2) sym parameter cmos inputs (vccq = 2.3 v - 3.6 v) ttl inputs (vccq = 2.4 v - 3.6 v) unit test conditions notes typ max typ max i li input load current - 1 - 2 a vcc = vcc max vccq = vccq max v in = vccq or v ss 1,6 i lo output leakage current dq[15:0], wait - 1 - 10 a vcc = vcc max vccq = vccq max v in = vccq or v ss i ccs , i ccd vcc standby, power-down 64-mbit 35 120 710 2000 a vcc = vcc max vccq = vcc max ce# =vccq rst# = vccq (for i ccs ) rst# = v ss (for i ccd ) wp# = v ih 1,2 128-mbit 55 120 710 2000 i ccr average vcc read current asynchronous single- word f = 5 mhz (1 clk) 20 25 - - ma 8-word read vcc = vcc max ce# = v il oe# = v ih inputs: v il or v ih 1 page-mode read f = 13 mhz (17 clk) 12 16 - - ma 8-word read synchronous burst f = 52 mhz, lc=4 16 19 - - ma 4-word read 19 22 - - ma 8-word read 22 26 - - ma 16-word read 23 28 - - ma continuous read i ccw, i cce vcc program current, vcc erase current 35 50 35 50 ma vpp = v ppl , pgm/ers in progress 1,3,5 26 33 26 33 vpp = v pph , pgm/ers in progress 1,3,5 i ccws, i cces vcc program suspend current, vcc erase suspend current 64-mbit 35 120 710 2000 a ce# = vccq; suspend in progress 1,3,4 128-mbit 55 120 710 2000 i pps, i ppws, ippes vpp standby current, vpp program suspend current, vpp erase suspend current 0.2 5 0.2 5 a vpp = v ppl , suspend in progress 1,3,7 i ppr vpp read 2 15 2 15 a vpp = v ppl 1,3 i ppw vpp program current 0.05 0.10 0.05 0.10 ma vpp = v ppl, program in progress 3 510510 vpp = v pph, program in progress i ppe v pp erase current 0.05 0.10 0.05 0.10 ma vpp = v ppl, erase in progress 3 510510 vpp = v pph, erase in progress
datasheet jul 2011 47 order number:208034-04 p33-65nm sbc 14.2 dc voltage characteristics i ppbc vpp blank check 0.05 0.10 0.05 0.10 ma vpp = v ppl 3 5 10 5 10 vpp = v pph notes: 1. all currents are rms unless noted. typical values at typical vcc, t c = +25 c. 2. i ccs is the average current measured over any 5 ms time interval 5 s after ce# is deasserted. 3. sampled, not 100% tested. 4. i cces is specified with the device deselected. if devi ce is read while in erase suspend, current is i cces plus i ccr . 5. i ccw , i cce measured over typical or max times specified in section 15.5, ?program and erase characteristics? on page 58 . 6. if v in > vcc the input load current increases to 10a max. 7. the i pps, i ppws, i ppes will increase to 200a when vpp/wp# is at v pph . table 21: dc voltage characteristics sym parameter cmos inputs (vccq = 2.3 v ? 3.6 v) ttl inputs (1) (vccq = 2.4 v ? 3.6 v) unit test conditions notes min max min max v il input low voltage -0.5 0.4 -0.5 0.6 v - 2 v ih input high voltage vccq ? 0.4 vccq + 0.5 2.0 vccq + 0.5 v - v ol output low voltage - 0.2 - 0.2 v vcc = vcc min vccq = vccq min i ol = 100 a - v oh output high voltage vccq ? 0.2 - vccq ? 0.2 - v vcc = vcc min vccq = vccq min i oh = ?100 a - v pplk vpp lock-out voltage - 0.4 - 0.4 v - 3 v lko vcc lock voltage 1.5 - 1.5 - v - - v lkoq vccq lock voltage 0.9 - 0.9 - v - - v ppl vpp voltage supply (logic level) 1.5 3.6 1.5 3.6 v - - v pph buffered enhanced factory programming vpp 8.5 9.5 8.5 9.5 v - - notes: 1. synchronous read mode is not supported with ttl inputs. 2. v il can undershoot to ?0.4 v and v ih can overshoot to vccq + 0.4 v for durations of 20 ns or less. 3. vpp v pplk inhibits erase and program operations. do not use v ppl and v pph outside their valid ranges . table 20: dc current characteristics (sheet 2 of 2) sym parameter cmos inputs (vccq = 2.3 v - 3.6 v) ttl inputs (vccq = 2.4 v - 3.6 v) unit test conditions notes typ max typ max
p33-65nm datasheet jul 2011 48 order number: 208034-04 15.0 ac characteristics 15.1 ac test conditions note: ac test inputs are driven at vccq for logic "1" and 0 v for logic "0." input/output timing begins/ends at vccq/2. input rise and fall times (10% to 90%) < 5 ns. worst-case speed occurs at vcc = vcc min . notes: 1. see the following table for component values. 2. test configuration component value for worst case speed conditions. 3. c l includes jig capacitance . figure 14: ac input/output reference waveform figure 15: transient equivalent testing load circuit table 22: test configuration component value for worst case speed conditions test configuration c l (pf) vccq min standard test 30 figure 16: clock input ac waveform io_ref.wmf input v ccq /2 v ccq /2 output v ccq 0v test points device under test out c l clk [c] v ih v il r203 r202 r201
datasheet jul 2011 49 order number:208034-04 p33-65nm sbc 15.2 capacitance 15.3 ac read specifications table 23: capacitance symbol parameter signals min typ max unit condition notes c in input capacitance address, data, ce#, we#, oe#, rst#, clk, adv#, wp# 26 7 pf typ temp = 25 c, max temp = 85 c, vcc = (0 v - 3.6 v), vccq = (0 v - 3.6 v), discrete silicon die 1,2,3 c out output capacitance data, wait 2 4 5 pf notes: 1. capacitance values are for a single die; for dual die, the capacitance values are doubled. 2. sampled, not 100% tested. 3. silicon die capacitance only, add 1 pf for discrete packages. table 24: ac read specifications - (sheet 1 of 2) num symbol parameter min max unit notes asynchronous specifications r1 t avav read cycle time easy bga 60 - ns - tsop 70 - ns - r2 t avqv address to output valid easy bga - 60 ns - tsop 70 ns - r3 t elqv ce# low to output valid easy bga - 60 ns - tsop 70 ns - r4 t glqv oe# low to output valid - 25 ns 1,2 r5 t phqv rst# high to output valid - 150 ns 1 r6 t elqx ce# low to output in low-z 0 - ns 1,3 r7 t glqx oe# low to output in low-z 0 - ns 1,2,3 r8 t ehqz ce# high to output in high-z - 20 ns 1,3 r9 t ghqz oe# high to output in high-z - 15 ns r10 t oh output hold from first occurring address, ce#, or oe# change 0-ns r11 t ehel ce# pulse width high 17 - ns 1 r12 t eltv ce# low to wait valid - 17 ns r13 t ehtz ce# high to wait high-z - 20 ns 1,3 r15 t gltv oe# low to wait valid - 17 ns 1 r16 t gltx oe# low to wait in low-z 0 - ns 1,3 r17 t ghtz oe# high to wait in high-z - 20 ns latching specifications r101 t avvh address setup to adv# high 10 - ns 1 r102 t elvh ce# low to adv# high 10 - ns 1 r103 t vlqv adv# low to output valid easy bga - 60 ns 1 tsop - 70 ns 1
p33-65nm datasheet jul 2011 50 order number: 208034-04 r104 t vlvh adv# pulse width low 10 - ns 1 r105 t vhvl adv# pulse width high 10 - ns 1 r106 t vhax address hold from adv# high 9 - ns 1,4 r108 t apa page address access - 25 ns 1 r111 t phvh rst# high to adv# high 30 - ns clock specifications r200 f clk clk frequency easy bga - 52 mhz 1,3,5,6 tsop - 40 mhz r201 t clk clk period easy bga 19.2 - ns tsop 25 - ns r202 t ch/cl clk high/low time easy bga 5 - ns tsop 9 - ns r203 t fclk/rclk clk fall/rise time 0.3 3 ns synchronous specifications (5) r301 t avch/l address setup to clk 9 - ns 1,6 r302 t vlch/l adv# low setup to clk 9 - ns 1,6 r303 t elch/l ce# low setup to clk 9 - ns 1,6 r304 t chqv / tclqv clk to output valid easy bga - 17 ns 1,6 tsop - 20 ns 1,6 r305 t chqx output hold from clk easy bga 3 - ns 1,6 tsop 5 - ns 1,6 r306 t chax address hold from clk 10 - ns 1,4,6 r307 t chtv clk to wait valid easy bga - 17 ns 1,6 tsop - 20 ns 1,6 r311 t chvl clk valid to adv# setup 3 - ns 1 r312 t chtx wait hold from clk easy bga 3 - ns 1,6 tsop 5 - ns 1,6 notes: 1. see figure 14, ?ac input/output reference waveform? on page 48 for timing measurements and max allowable input slew rate. 2. oe# may be delayed by up to t elqv ? t glqv after ce#?s falling edge without impact to t elqv. 3. sampled, not 100% tested. 4. address hold in synchronous burst read mode is t chax or t vhax , whichever timing specification is satisfied first. 5. synchronous burst read mode is not supported with ttl level inputs. 6. applies only to subsequent synchronous reads. table 24: ac read specifications - (sheet 2 of 2) num symbol parameter min max unit notes
datasheet jul 2011 51 order number:208034-04 p33-65nm sbc note: wait shown deasserted during asynchronous read mode (rcr.10=0, wait asserted low). note: wait shown deasserted during asynchronous read mode (rcr.10=0, wait asserted low) figure 17: asynchronous single-word read (adv# low) figure 18: asynchronous single-word read (adv# latch) r5 r7 r6 r17 r15 r9 r4 r8 r3 r1 r2 r1 address [a] adv#[v] ce# [e] oe# [g] wait [t] data [d/q] rst# [p] 105 r1 0 r7 r6 r1 7 r15 r9 r4 r8 r3 r1 0 6 r1 0 1 r r2 r1 address [a] a[3:1] [a] adv#[v] ce# [e] oe# [g] wait [t] data [d/q] 104 r
p33-65nm datasheet jul 2011 52 order number: 208034-04 note: wait shown deasserted during asynchronous read mode (rcr.10=0, wait asserted low). . notes: 1. wait is driven per oe# assertion during synchronous array or non-array read, and can be configured to assert either during or one data cycle before valid data. 2. this diagram illustrates the case in which an n-word burst is initiated to the flash memory array and it is terminated by ce# deassertion after the first word in the burst. figure 19: asynchronous page-mode read timing valid address 0 1 2 7 q0 q1 q2 q7 r108 r108 r108 r13 r6 r9 r4 r8 r3 r106 r101 r105r105 r10 r10 r10 r10 r2 a[max:4] [a] a[3:1] adv# [v] ce# [e] oe# [g] wait [t] data [d/q] figure 20: synchronous single-word array or non-array read timing r312 r305 r304 r4 r17 r307 r15 r9 r7 r8 r303 r102 r3 r104 r106 r101 r104 r105 r105 r2 r306 r301 clk [c] a ddress [a] adv# [v] ce# [e] oe# [g] wait [t] data [d/q]
datasheet jul 2011 53 order number:208034-04 p33-65nm sbc notes: 1. wait is driven per oe# assertion during synchronous array or non-array read, and can be configured to assert either during or one data cycle before valid data. 2. at the end of word line; the delay incurred when a burst access crosses a 16-word boundary and the starting address is not 4-word boundary aligned. see section 11.1.3, ?end of word line (eowl) considerations? on page 36 for more information. note: wait is driven per oe# assertion during synchronous array or non-array read. wait asserted during initial latency and deasserted during valid data (rcr.10=0, wait asserted low). figure 21: continuous burst read, showing an output delay timing figure 22: synchronous burst-mode four-word read timing r305 r305 r305 r305 r304 r4 r7 r312 r307 r15 r303 r102 r3 r106 r105 r105 r101 r2 r304 r304 r304 r306 r302 r301 clk [c] a ddress [a] adv# [v] ce# [e] oe# [g] wait [t] data [d/q] y a q0 q1 q2 q3 r307 r10 r304 r305 r304 r4 r7 r17 r15 r9 r8 r303 r3 r106 r102 r105 r105 r101 r2 r306 r302 r301 clk [c] a ddress [a] adv# [v] ce# [e] oe# [g] wait [t] data [d/q]
p33-65nm datasheet jul 2011 54 order number: 208034-04 15.4 ac write specifications table 25: ac write specifications num symbol parameter min max unit notes w1 t phwl rst# high recovery to we# low 150 - ns 1,2,3 w2 t elwl ce# setup to we# low 0 - ns 1,2,3 w3 t wlwh we# write pulse width low 50 - ns 1,2,4 w4 t dvwh data setup to we# high 50 - ns 1,2, 12 w5 t avwh address setup to we# high 50 - ns 1,2 w6 t wheh ce# hold from we# high 0 - ns w7 t whdx data hold from we# high 0 - ns w8 t whax address hold from we# high 0 - ns w9 t whwl we# pulse width high 20 - ns 1,2,5 w10 t vpwh vpp setup to we# high 200 - ns 1,2,3,7 w11 t qvvl vpp hold from status read 0 - ns w12 t qvbl wp# hold from status read 0 - ns 1,2,3,7 w13 t bhwh wp# setup to we# high 200 - ns w14 t whgl we# high to oe# low 0 - ns 1,2,9 w16 t whqv we# high to read valid t avqv + 35 - ns 1,2,3,6,10 write to asynchronous read specifications w18 t whav we# high to address valid 0 - ns 1,2,3,6,8 write to synchronous read specifications w19 t whch/l we# high to clock valid 19 - ns 1,2,3,6,10 w20 t whvh we# high to adv# high 19 - ns write specifications with clock active w21 t vhwl adv# high to we# low - 20 ns 1,2,3,11 w22 t chwl clock high to we# low - 20 ns notes: 1. write timing characteristics during erase suspend are the same as write-only operations. 2. a write operation can be terminated with either ce# or we#. 3. sampled, not 100% tested. 4. write pulse width low (t wlwh or t eleh ) is defined from ce# or we# low (whichever occurs last) to ce# or we# high (whichever occurs first). hence, t wlwh = t eleh = t wleh = t elwh . 5. write pulse width high (t whwl or t ehel ) is defined from ce# or we# high (whichever occurs first) to ce# or we# low (whichever occurs last). hence, t whwl = t ehel = t whel = t ehwl ). 6. t whvh or t whch/l must be met when transiting from a write cycle to a synchronous burst read. 7. vpp and wp# should be at a valid level until erase or program success is determined. 8. this specification is only ap plicable when transiting from a write cycle to an asynchronous read. see spec w19 and w20 for synchronous read. 9. when doing a read status operation following any command that alters the status register, w14 is 20 ns. 10. add 10 ns if the write operations results in a rcr or bloc k lock status change, for the subsequent read operation to reflect this change. 11. these specs are required only when the device is in a synchronous mode and clock is active during address setup phase. 12. this specification must be complied with by customer?s writ ing timing. the result would be unpredictable if any violation to this timing specification.
datasheet jul 2011 55 order number:208034-04 p33-65nm sbc note: wait deasserted during asynchronous read and during write. wait high-z during write per oe# deasserted. figure 23: write-to-write timing figure 24: asynchronous read-to-write timing w1 w7 w4 w7 w4 w3 w9 w3 w9 w3w3 w6 w2 w6 w2 w8 w8 w5 w5 address [a] ce# [e] we# [w] oe# [g] data [d/q] rst# [p] q d r5 w7 w4 r10 r7 r6 r17 r15 w6 w3w3 w2 r9 r4 r8 r3 w8 w5 r1 r2 r1 address [a] ce# [e] oe# [g] we# [w] wait [t] data [d/q] rst# [p]
p33-65nm datasheet jul 2011 56 order number: 208034-04 note: wait shown deasserted and high-z per oe# deassertion during write operation (rcr 10=0, wait asserted low). clock is ignored during write operation. figure 25: write-to-asynchronous read timing figure 26: synchronous read-to-write timing d q w1 r9 r8 r4 r3 r2 w7 w4 r17 r15 w14 w18 w3w3 r10 w6 w2 r1r1 w8 w5 address [a] adv# [v] ce# [e] we# [w] oe# [g] wait [t] data [d/q] rst# [p] latency count q d d w7 r305 r304 r7 r312 r307 r16 w15 w22 w21 w9 w8 w9 w3 w22 w21 w3 w2 r8 r4 w6 r11 r13 r11 r303 r3 r104r104 r106 r102 r105r105 w18 w5 r101 r2 r306 r302 r301 clk [c ] address [a] adv# [v] ce# [e] oe# [g] we#[ w] wait [t] data [ d/q]
datasheet jul 2011 57 order number:208034-04 p33-65nm sbc note: wait shown deasserted and high-z per oe# deassertion during write operation (rcr.10=0, wait asserted low). figure 27: write-to-synchronous read timing latency count d q q w1 r304 r305 r304 r3 w7 w4 r307 r15 r4 w20 w19 w18 w3w3 r11 r303 r11 w6 w2 r104 r106 r104 r306 w8 w5 r302 r301 r2 clk[c] address [a] adv#[v] ce# [ e] we# [w ] oe# [g] wait [t ] data [d /q] rst# [ p]
p33-65nm datasheet jul 2011 58 order number: 208034-04 15.5 program and erase characteristics table 26: program and erase specifications num symbol parameter v ppl v pph unit note min typ max min typ max conventional word programming w200 t prog/w program time single word - 40 175 - 40 175 s 1 buffered programming w250 t prog/ buffer program time aligned 16-wd, bp time (32 words) - 70 200 - 70 200 s 1 aligned 32-wd, bp time (32 word) - 85 200 - 85 200 one full buffer (256 words) - 284 1280 - 160 800 buffered enhanced factory programming w451 t befp/b program single byte n/a n/a n/a - 0.31 - s 1,2 w452 t befp/setup befp setup n/a n/a n/a 10 - - 1 erase and suspend w500 t ers/pb erase time 32-kbyte parameter - 0.4 2.5 - 0.4 2.5 s 1 w501 t ers/mb 128-kbyte main - 0.5 4.0 - 0.5 4.0 w600 t susp/p suspend latency program suspend - 20 25 - 20 25 s w601 t susp/e erase suspend - 20 25 - 20 25 w602 t ers/susp erase to suspend - 500 - - 500 - 1,3 blank check w702 t bc/mb blank check main array block - 3.2 - - 3.2 - ms - notes: 1. typical values measured at t c = +25 c and nominal voltages. performanc e numbers are valid for all speed versions. excludes system overhead. sampled, but not 100% tested. 2. averaged over entire device. 3. w602 is the typical time between an initial block erase or erase resume command and the a subsequent erase suspend command. violating the specification repeatedly during any particular block erase may cause erase failures.
datasheet jul 2011 59 order number:208034-04 p33-65nm sbc 16.0 ordering information note: the last digit is randomly assigned to cover packing medi a and/or features or other specific configuration. for further information on ordering products or for product part numbers, go to: http://www.micron.com/partscatalog.html?categor ypath=products/nor_flash/parallel_nor_flash figure 28: decoder for p33-65nm (sbc) products f 1 2 p 3 3 b 8 s 2 j 8 product line designator 28f = numonyx ? flash memory package designator js = 56- lead tsop, lead-free rc = 64-ball easy bga, leaded pc = 64 -ball easy bga, lead-free device density 128 = 128-mbit product family p 33 = numonyx ? flash memory (p33) v cc = 2.3? 3.6v v ccq = 2. 3? 3. 6 v device details 65 nm lithography parameter location b = bottom parameter t = top parameter f 640 = 64 - mbit 7 0 speed 60ns 70ns * device features* table 27: valid combinations for discrete products 64-mbit 128-mbit rc28f640p33tf60* rc28f128p33tf60* rc28f640p33bf60* rc28f128p33bf60* pc28f640p33tf60* pc28f128p33tf60* pc28f640p33bf60* pc28f128p33bf60* js28f640p33tf70* js28f128p33tf70* js28f640p33bf70* JS28F128P33BF70*
p33-65nm datasheet jul 2011 60 order number: 208034-04 appendix a supplemental reference information a.1 common flash interface the common flash interface (cfi) is part of an overall specification for multiple command-set and control-interface descriptions. this appendix describes the database structure containing the data returned by a read operation after issuing the read cfi command (see section 6.2, ?device command bus cycles? on page 18 ). system software can parse this database structure to obtain information about the flash device, such as block size, density, bus width, and electrical specifications. the system software will then know which command set(s) to use to properly perform flash writes, block erases, reads and otherwise control the flash device. a.1.1 query structure output the query database allows system software to obtain information for controlling the flash device. this section describes the device?s cfi-compliant interface that allows access to query data. query data are presented on the lowest-order data outputs (dq 7-0 ) only. the numerical offset value is the address relative to the maximum bus width supported by the device. on this family of devices, the query table device starting address is a 10h, which is a word address for x16 devices. for a word-wide (x16) device, the first two query-structure bytes, ascii ?q? and ?r,? appear on the low byte at word addresses 10h and 11h. this cfi-compliant device outputs 00h data on upper bytes. the device outputs ascii ?q? in the low byte (dq 7-0 ) and 00h in the high byte (dq 15-8 ). at query addresses containing two or more bytes of information, the least significant data byte is presented at the lower addre ss, and the most significant data byte is presented at the higher address. in all of the following tables, addresses and data are represented in hexadecimal notation, so the ?h? suffix has been dropped. in addition, since the upper byte of word- wide devices is always ?00h,? the leading ?00? has been dropped from the table notation and only the lower byte value is shown. any x16 device outputs have 00h on the upper byte in this mode. table 28: summary of query structure output as a function of device and mode device hex offset hex code ascii v alue 00010: 51 "q" device addresses 00011: 52 "r" 00012: 59 "y"
datasheet jul 2011 61 order number:208034-04 p33-65nm sbc table 29: example of query structure output of x16 devices a.1.2 query structure overview the query command causes the flash component to display the common flash interface (cfi) query structure or database . ta b l e 3 0 summarizes the structure sub-sections and address locations. table 30: query structure note: 1. refer to the query structure output section and offset 28h for the detailed definition of offset address as a function of device bus width and mode. 2. ba = block address beginning location (i.e., 08000h is block 1?s beginning location when the block size is 32-kword). 3. offset 15 defines ?p? which points to the pr imary numonyx-specific extended query table. a.1.3 read cfi identification string the identification string provides verification that the component supports the common flash interface specification. it also indicates the specification version and supported vendor-specified command set(s). offset hex code value a x -a 1 d 15 -d 0 00010h 0051 ?q? 00011h 0052 ?r? 00012h 0059 ?y? 00013h p_id lo prvendor id# 00014h p_id hi 00015h p lo prvendor tbladr 00016h p hi 00017h a_id lo altvendor id# 00018h a_id hi ... ... ... 00001-fh reserved reserved for vendor-specific information 00010h cfi query identification string command set id and vendor data offset 0001bh system interface information device timing & voltage information 00027h device geometry definition flash device layout p (3) primary numonyx-specific extended query vendor-defined additional information specific to the primary vendor algorithm
p33-65nm datasheet jul 2011 62 order number: 208034-04 table 31: cfi identification offset length description add. hex code value 10h 3 query-unique ascii string ?qry? 10: 11: 12: -51 -52 -59 ?q? ?r? ?y? 13h 2 primary vendor command set and control interface id code. 16-bit id code for vendor-specified algorithms 13: 14: -01 -00 15h 2 extended query table primary algorithm address 15: 16: -0a -01 17h 2 alternate vendor command set and control interface id code. 0000h means no second vendor-specified algorithm exists 17: 18: -00 -00 19h 2 secondary algorithm extended query table address. 0000h means none exists 19: 1a: -00 -00
datasheet jul 2011 63 order number:208034-04 p33-65nm sbc table 32: system interface information offset length description add hex code value 1bh 1 vcc logic supply minimum program/erase voltage bits 0-3 bcd 100 mv bits 4-7 bcd volts 1b: -23 2.3v 1ch 1 vcc logic supply maximum program/erase voltage bits 0-3 bcd 100 mv bits 4-7 bcd volts 1c: -36 3.6v 1dh 1 vpp [programming] supply minimum program/erase voltage bits 0-3 bcd 100 mv bits 4-7 hex volts 1d: -85 8.5v 1eh 1 vpp [programming] supply maximum program/erase voltage bits 0-3 bcd 100 mv bits 4-7 hex volts 1e: -95 9.5v 1fh 1 ?n? such that typical single word program time-out = 2 n -sec 1f: -06 64 s 20h 1 ?n? such that typical full buffer write time-out = 2 n -sec 20: -09 512 s 21h 1 ?n? such that typical block erase time-out = 2 n m-sec 21: -09 0.5s 22h 1 ?n? such that typical full chip erase time-out = 2 n m-sec 22: -00 na 23h 1 ?n? such that maximum word program time-out = 2 n times typical 23: -02 256 s 24h 1 ?n? such that maximum buffer write time-out = 2 n times typical 24: -02 2048 s 25h 1 ?n? such that maximum block erase time-out = 2 n times typical 25: -03 4s 26h 1 ?n? such that maximum chip erase time-out = 2 n times typical 26: -00 na
p33-65nm datasheet jul 2011 64 order number: 208034-04 a.1.4 device geometry definition table 33: device geometry definition offset length description add hex code value 27h 1 ?n? such that device size = 2 n in number of bytes 27: see table below 28h 2 flash device interface code assignment: "n" such that n+1 specifies the bit field that represents the flash device width capabilities as descr ibed in the table: 76543210 _ _ _ _ x64 x32 x16 x8 28: -01 x16 15 14 13 12 11 10 9 8 ________29:-00 2ah 2 ?n? such that maximum number of bytes in write buffer = 2 n 2a: -09 512 2b: -00 2ch 1 number of erase block regions (x) within device: 1. x = 0 means no erase blocking; the device erases in bulk 2. x specifies the number of device regions with one or more contiguous same-size erase blocks. 3. symmetrically blocked partitions have one blocking region 2c: see table below 2d 4 erase block region 1 information bits 0-15 = y, y+1 = number of identical-size erase blocks bits 16-31 = z, region erase block(s) size are z x 256 bytes 2d: see table below 2e: 2f: 30: 31h 4 erase block region 2 information bits 0-15 = y, y+1 = number of identical-size erase blocks bits 16-31 = z, region erase block(s) size are z x 256 bytes 31: see table below 32: 33: 34: 35h 4 reserved for future erase block region information 35: see table below 36: 37: 38: address 64-mbit 128-mbit address 64-mbit 128-mbit -b -t -b -t -b -t -b -t 27: -17 -17 -18 -18 30: -00 -02 -00 -02 28: -01 -01 -01 -01 31: -3e -03 -7e -03 29: -00 -00 -00 -00 32: -00 -00 -00 -00 2a -09 -09 -09 -09 33: -00 -80 -00 -80 2b -00 -00 -00 -00 34: -02 -00 -02 -00 2c: -02 -02 -02 -02 35: -00 -00 -00 -00 2d: -03 -3e -03 -7e 36: -00 -00 -00 -00 2e: -00 -00 -00 -00 37: -00 -00 -00 -00 2f: -80 -00 -80 -00 38: -00 -00 -00 -00
datasheet jul 2011 65 order number:208034-04 p33-65nm sbc a.1.5 numonyx-specific extended query table table 34: primary vendor-specific extended query: offset p=10ah length description (optional flash features and commands) add. hex code value (p+0)h 3 primary extended query table unique ascii string ?pri? 10a: -50 ?p? (p+1)h 10b: -52 ?r? (p+2)h 10c: -49 ?i? (p+3)h 1 major version number, ascii 10d: -31 ?1? (p+4)h 1 minor version number, ascii 10e: -35 ?5? (p+5)h 4 optional feature and command support (1=yes, 0=no) 10f: -e6 (p+6)h bits 10-31 are reserved; undefined bits are ?0?. if bit 31 110 (1) :-01 (p+7)h ?1?then another 31 bit field of optional features follows at 111: -00 (p+8)h the end of the bit-30 field. 112: - 00 bit 0 chip erase supported bit 0 = 0 no bit 1 suspend erase supported bit 1 = 1 yes bit 2 suspend program supported bit 2 = 1 yes bit 3 legacy lock/unlock supported bit 3 = 0 no bit 4 queued erase supported bit 4 = 0 no bit 5 instant individual bloc k locking supported bit 5 = 1 yes bit 6 protection bits supported bit 6 = 1 yes bit 7 pagemode read supported bit 7 = 1 yes bit 8 synchronous read supported tsop bit 8 = 0 no bga bit 8 = 1 yes bit 9 simultaneous operations supported bit 9 = 0 no bit 10 extended flash array blocks supported bit 10 = 0 no bit 11 permanent block locking of up to full main array supported bit 11 = 0 no bit 12 permanent block locking of up to partial main array supported bit 12 = 0 no bit 30 cfi link(s) to follow bit 30 = 0 no bit 31 another "optional features" field to follow bit 31 = 0 no (p+9)h 1 supported functions after suspend: read array, status, query other supported operations are: bits 1-7 reserved; undefined bits are ?0? 113: -01 bit 0 program supported after erase suspend bit 0 = 1 yes (p+a)h 2 block status register mask 114: -03 (p+b)h bits 2-15 are reserved; undefined bits are ?0? 115: -00 bit 0 block lock-bit status register active bit 0 = 1 yes bit 1 block lock-down bit status active bit 1 = 1 yes bit 4 efa block lock-bit status register active bit 4 = 0 no
p33-65nm datasheet jul 2011 66 order number: 208034-04 note: 1. address 0x110 for tsop: -00; address 0x110 for bga: -01. table 35: otp register information bit 5 efa block lock-down bit status active bit 5 = 0 no (p+c)h 1 vcc logic supply highest performance program/erase voltage bits 0-3 bcd value in 100 mv bits 4-7 bcd value in volts 116: -30 3.0v (p+d)h 1 vpp optimum program/erase supply voltage bits 0-3 bcd value in 100 mv bits 4-7 hex value in volts 117: -90 9.0v offset (1) p=10ah length description (optional flash features and commands) add. hex code value (p+e)h 1 number of protection register fields in jedec id space. ?00h,? indicates that 256 prot ection fields are available 118: -02 2 (p+f)h (p+10)h (p+11)h (p+12)h 4 protection field 1: protection description this field describes user-available one time programmable (otp) protection register bytes. some are pre-programmed with device-unique serial numbers. others are user programmable. bits 0?15 point to the protection register lock byte, the section?s first byte. the following bytes are factory pre-programmed and user-programmable. bits 0?7 = lock/bytes jedec-plane physical low address bits 8?15 = lock/bytes jedec-plane physical high address bits 16?23 = ?n? such that 2 n = factory pre-programmed bytes bits 24?31 = ?n? such that 2 n = user programmable bytes 119: 11a: 11b: 11c: -80 -00 -03 -03 80h 00h 8 byte 8 byte (p+13)h (p+14)h (p+15)h (p+16)h (p+17)h (p+18)h (p+19)h (p+1a)h (p+1b)h (p+1c)h 10 protection field 2: protection description bits 0?31 point to the protection register physical lock-word address in the jedec-plane. following bytes are factory or user-programmable. 11d: 11e: 11f: 120: -89 -00 -00 -00 89h 00h 00h 00h bits 32?39 = ?n? such that n = factory pgm'd groups (low byte) bits 40?47 = ?n? such that n = factory pgm'd groups (high byte) bits 48?55 = ?n? \ 2 n = factory programmable bytes/group 121: 122: 123: -00 -00 -00 0 0 0 bits 56?63 = ?n? such that n = user pgm'd groups (low byte) bits 64?71 = ?n? such that n = user pgm'd groups (high byte) bits 72?79 = ?n? such that 2 n = user programmable bytes/ group 124: 125: 126: -10 -00 -04 16 0 16 offset p=10ah length description (optional flash features and commands) add. hex code value
datasheet jul 2011 67 order number:208034-04 p33-65nm sbc table 37: partition and erase block region information table 36: burst read information offset p=10ah length description (optional flash features and commands) add. hex code value (p+1d)h 1 page mode read capability bits 0-7 = ?n? such that 2 n hex value represents the number of read-page bytes. see offset 28h for device word width to determine page-mode data output width. 00h indicates no read page buffer. 127: -04 16 byte (p+1e)h 1 number of synchronous mode read configuration fields that follow. 00h indicates no burst capability. 128: -04 4 (p+1f)h 1 synchronous mode read capability configuration 1 bits 3-7 = reserved bits 0-2 ?n? such that 2 n+1 hex value represents the maximum number of continuous synchronous reads when the device is configured for its maximum word width. a value of 07h indicates that the device is capable of continuous linear bursts that will output data until the internal burst counter reaches the end of the device?s burstable address space. this field?s 3-bit value can be written directly to the read configuration register bits 0-2 if the device is configured for its maximum word width. see offset 28h for word width to determine the burst data output width. 129: -01 4 (p+20)h 1 synchronous mode read capability configuration 2 12a: -02 8 (p+21)h 1 synchronous mode read capability configuration 3 12b: -03 16 (p+22)h 1 synchronous mode read capability configuration 4 12c: -07 cont offset (1) see table be low p = 10ah description address bottom top (optional flash features and commands) len bot top (p+23)h (p+23)h 112d:12d: number of device hardw are-partition regions w ithin the device. x = 0: a single hardw are partition device (no f ields follow ). x specifies the number of device partition regions containing one or more contiguous erase block regions.
p33-65nm datasheet jul 2011 68 order number: 208034-04 table 38: partition region 1 information (sheet 1 of 2) off s e t (1) see table below p = 10ah description address bottom top (optional flash features and commands) len bot top (p+24)h (p+24)h data size of this parition region inf ormation f ield 2 12e: 12e (p+25)h (p+25)h (# addressable locations, including this f ield) 12f 12f (p+26)h (p+26)h number of identical partitions w ithin the partition region 2 130: 130: (p+27)h (p+27)h 131: 131: (p+28)h (p+28)h 1 132: 132: (p+29)h (p+29)h 1 133: 133: (p+2a)h (p+2a)h 1 134: 134: (p+2b)h (p+2b)h 1 135: 135: types of erase block regions in this partition region. x = 0 = no erase blocking; the partition region erases in bulk x = number of erase block regions w / contiguous same-size erase blocks. symmetrically blocked partitions have one blocking region. partition size = (type 1 blocks)x(type 1 block sizes) + (type 2 blocks)x(type 2 block sizes) +?+ (type n blocks)x(type n block sizes) number of program or erase operations allow ed in a partition bits 0?3 = number of simultaneous program operations bits 4?7 = number of simultaneous erase operations simultaneous program or erase operations allow ed in other partitions w hile a partition in this region is in program mode bits 0?3 = number of simultaneous program operations bits 4?7 = number of simultaneous erase operations simultaneous program or erase operations allow ed in other partitions w hile a partition in this region is in erase mode bits 0?3 = number of simultaneous program operations bits 4?7 = number of simultaneous erase operations
datasheet jul 2011 69 order number:208034-04 p33-65nm sbc table 39: partition region 1 information (sheet 2 of 2) offset (1) see table below p = 10ah description address bottom top (optional flash features and commands) len bot top (p+2c)h (p+2c)h partition region 1 erase block type 1 information 4 136: 136: (p+2d)h (p+2d)h bits 0?15 = y, y+1 = # identical-size erase blks in a partition 137: 137: (p+2e)h (p+2e)h bits 16?31 = z, region erase block(s) size are z x 256 bytes 138: 138: (p+2f)h (p+2f)h 139: 139: (p+30)h (p+30)h partition 1 (erase block type 1) 2 13a: 13a: (p+31)h (p+31)h block erase cycles x 1000 13b: 13b: (p+32)h (p+32)h 1 13c: 13c: (p+33)h (p+33)h 1 13d: 13d: partition region 1 (erase block type 1) programming region inf ormation 6 (p+34)h (p+34)h bits 0?7 = x, 2^x = programming region aligned size ( bytes ) 13e: 13e: (p+35)h (p+35)h bits 8?14 = reserved; bit 15 = legacy f lash operation (ignore 0:7) 13f: 13f: (p+36)h (p+36)h bits 16?23 = y = control mode valid size in bytes 140: 140: (p+37)h (p+37)h bits 24-31 = reserved 141: 141: (p+38)h (p+38)h bits 32-39 = z = control mode invalid size in bytes 142: 142: (p+39)h (p+39)h bits 40-46 = reserved; bit 47 = legacy flash operation (ignore 23:16 & 39:32) 143: 143: (p+3a)h (p+3a)h partition region 1 erase block type 2 information 4 144: 144: (p+3b)h (p+3b)h bits 0?15 = y, y+1 = # identical-size erase blks in a partition 145: 145: (p+3c)h (p+3c)h bits 16?31 = z, region erase block(s) size are z x 256 bytes 146: 146: (p+3d)h (p+3d)h 147: 147: (p+3e)h (p+3e)h partition 1 (erase block type 2) 2 148: 148: (p+3f)h (p+3f)h block erase cycles x 1000 149: 149: (p+40)h (p+40)h 1 14a: 14a: (p+41)h (p+41)h 1 14b: 14b: partition region 1 (erase block type 2) programming region inf ormation 6 (p+42)h (p+42)h bits 0?7 = x, 2^x = programming region aligned size ( bytes ) 14c: 14c: (p+43)h (p+43)h bits 8?14 = reserved; bit 15 = legacy f lash operation (ignore 0:7) 14d: 14d: (p+44)h (p+44)h bits 16?23 = y = control mode valid size in bytes 14e: 14e: (p+45)h (p+45)h bits 24-31 = reserved 14f: 14f: (p+46)h (p+46)h bits 32-39 = z = control mode invalid size in bytes 150: 150: (p+47)h (p+47)h bits 40-46 = reserved; bit 47 = legacy flash operation (ignore 23:16 & 39:32) 151: 151: partition 1 (erase block type 2) bits per cell; internal edac bits 0?3 = bits per cell in erase region bit 4 = internal edac used (1=yes, 0=no) bits 5?7 = reserve for f uture use partition 1 (erase block type 2) page mode and synchronous mode capabilities def ined in table 10. bit 0 = page-mode host reads permitted (1=yes, 0=no) bit 1 = synchronous host reads permitted (1=yes, 0=no) bit 2 = synchronous host w rites permitte partition 1 (erase block type 1) page mode and synchronous mode capabilities def ined in table 10. bit 0 = page-mode host reads permitted (1=yes, 0=no) bit 1 = synchronous host reads permitted (1=yes, 0=no) bit 2 = synchronous host w rites permitted (1=yes, 0=no) bits 3?7 = reserved f or f uture use partition 1 (erase block type 1) bits per cell; internal edac bits 0?3 = bits per cell in erase region bit 4 = internal edac used (1=yes, 0=no) bits 5?7 = reserve for f uture use
p33-65nm datasheet jul 2011 70 order number: 208034-04 table 40: partition and erase block region information add 64-mbit 128-mbit -b -t -b -t 12d: -01 -01 -01 -01 12e: -24 -24 -24 -24 12f: -00 -00 -00 -00 130: -01 -01 -01 -01 131: -00 -00 -00 -00 132: -11 -11 -11 -11 133: -00 -00 -00 -00 134: -00 -00 -00 -00 135: -02 -02 -02 -02 136: -03 -3e -03 -7e 137: -00 -00 -00 -00 138: -80 -00 -80 -00 139: -00 -02 -00 -02 13a: -64 -64 -64 -64 13b: -00 -00 -00 -00 13c: -02 -02 -02 -02 13d: -03 -03 -03 -03 13e: -00 -00 -00 -00 13f: -80 -80 -80 -80 140: -00 -00 -00 -00 141: -00 -00 -00 -00 142 -00 -00 -00 -00 143: -80 -80 -80 -80 144: -3e -03 -7e -03 145: -00 -00 -00 -00 146: -00 -80 -00 -80 147: -02 -00 -02 -00 148: -64 -64 -64 -64 149: -00 -00 -00 -00 14a: -02 -02 -02 -02 14b: -03 -03 -03 -03 14c: -00 -00 -00 -00 14d: -80 -80 -80 -80 14e: -00 -00 -00 -00 14f: -00 -00 -00 -00 150: -00 -00 -00 -00 151: -80 -80 -80 -80
datasheet jul 2011 71 order number:208034-04 p33-65nm sbc table 41: cfi link information length description (optional flash features and commands) add. hex code value 4 cfi link field bit definitions bits 0-9 = address offset (within 32mbit segment) of referenced cfi table bits 10-27 = nth 32mbit segment of referenced cfi table bits 28-30 = memory type bit 31 = another cfi link field immediately follows 152: 153: 154: 155: -ff 1 cfi link field quantity subfield definitions bits 0-3 = quantity field (n such that n+1 equals quantity) bit 4 = table & die relative location bit 5 = link field & table relative location bits 6-7 = reserved 156: -ff
p33-65nm datasheet jul 2011 72 order number: 208034-04 a.2 flowcharts figure 29: word program flowchart start data cycle - address = location to program - data = data to program yes d7 = '1' ? end no suspend ? no yes errors ? yes no error-handler user defined routine read status register - toggle ce# or oe# to update status register - see status register flowchart program suspend see suspend/ resume flowchart command cycle - issue program command - address = location to program - data = 0x40 check ready status - read status register command not required - perform read operation - read ready status on signal d7
datasheet jul 2011 73 order number:208034-04 p33-65nm sbc figure 30: program suspend/resume flowchart read status register sr.7 = sr.2 = read array data program completed done reading program resumed read array data 0 no 0 yes 1 1 program suspend /resume procedure write program resume data = d0 h addr = suspended block (ba) bus operation command comments write program suspend data = b0h addr = x standby check sr .7 1 = wsm ready 0 = wsm busy standby check sr .2 1 = program suspended 0 = program completed write read array data = ffh addr = block address to read (ba) read read array data from block other than the one being programmed read status register data initiate a read cycle to update status register addr = suspended block (ba) pgm _sus .wmf start write b0h any address program suspend read status write 70h write ffh any address read array write d0h any address program resume write ffh read array write read status data = 70h addr = block to suspend (ba) write 70h any address read status any address
p33-65nm datasheet jul 2011 74 order number: 208034-04 figure 31: erase suspend/resume flowchart erase completed read array data 0 0 no read 1 program program loop read array data 1 start read status register sr[7] = sr[6] = erase resumed (1 ) read or program ? done write write idle idle write erase suspend read array or program none none erase resume data = 0 xb0 addr = any device address data = 0xff or 0x40 addr = any address within the suspended device check sr[7]: 1 = wsm ready 0 = wsm busy check sr[6]: 1 = erase suspended 0 = erase completed data = 0 xd0 addr = any device address bus operation command comments read none status register data . addr = any device address read or write none read array or program data from / to block other than the one being erased erase suspend / resume procedure if the suspended partition was placed in read array mode or a program loop : write 0xb0, any device address (erase suspend ) write 0x70, any device address (read status ) write 0xd0, any address (erase resume) write 0x70, any device address (read status ) write 0xff, any device address (read array) write read status data = 0 x70 addr = any device address yes write read status register return device to status mode : data = 0x70 addr = any device address note : 1. the t ers/susp timing between the initial block erase or erase resume command and a subsequent erase suspend command should be followed .
datasheet jul 2011 75 order number:208034-04 p33-65nm sbc figure 32: buffer program flowchart start get next target address issue write to buffer command e8h block address read status register block address (note 7) is wsm ready? sr. 7 = 1 = yes device supports buffer writes? set timeout or loop counter timeout or count expired ? write confirm d0h block address another buffered programming? yes no no write buffer data start address x = 0 yes 0 = n o no yes use single word programming abort bufferred program? no x = n? write buffer data address within buffer range x = x + 1 write to another block address buffered program aborted no yes yes write word count block address notes: 1. word count values on dq 0 -dq 15 are loaded into the count register. count ranges for this device are n =0000h to 00ffh. 2. the device outputs the status register when read . 3. write buffer contents will be programmed at the device start address or destination flash address . 4. align the start address on a write buffer boundary for maximum programming performance (i.e., a 8 -a 1 of the start address =0). 5. the device aborts the buffered program command if the current address is outside the original block address . 6. the status register indicates an ?improper command sequence? if the buffered program command is aborted . follow this with a clear status register command . 7. the device defaults to output sr data after the buffered programming setup command (e8h) is issued. ce# or oe# must be be toggled to update status register . don?t issue the read sr command (70h), which would be interpreted by the internal state machine as buffer word count . 8. full status check can be done after all erase and write sequences complete . write ffh after the last operation to reset the device to read array mode . . . . bus operation standby read command write write to buffer read (note 7) standby comments check sr .7 1 = wsm ready 0 = wsm busy status register data ce# and oe# low updates sr addr = block address data = e8h addr = block address sr. 7 = valid addr = block address check sr .7 1 = device wsm is busy 0 = device wsm is ready write program confirm data = d0h addr = block address write ( notes 1, 2) data = n- 1 = word count n = 0 corresponds to count = 1 addr = block address write ( notes 3, 4) data = write buffer data addr = start address write ( notes 5, 6) data = write buffer data addr = address within buffer rang e suspend program loop read status register sr. 7 =? full status check if desired program complete suspend program 1 0 no yes clear status register 50h address within device yes
p33-65nm datasheet jul 2011 76 order number: 208034-04 figure 33: befp flowchart sr error handler (user-defined) befp setup delay yes (sr.7=0) a issue befp setup cmd (data = 0x80) issue befp confirm cmd (data = 00d0h) read status register no (sr.7=1) exit start yes (sr.0=0) no (sr.0=1) write 0xffffh outside block no (sr.0=1) yes (sr.0=0) no yes yes (sr.7=1) no (sr.7=0) finish no yes befp setup done ? full status register check for errors read status register buffer ready ? write data word to buffer buffer full ? read status register program done ? program more data ? program/verify phase setup phase exit phase a b b befp exited ? read status register
datasheet jul 2011 77 order number:208034-04 p33-65nm sbc figure 34: block erase flowchart start confirm cycle - issue confirm command - address = block to be erased - data = erase confirm (0xd0) errors ? yes no error-handler user defined routine check ready status - read status register command not required - perform read operation - read ready status on signal sr.7 command cycle - issue erase command - address = block to be erased - data = 0x20 yes sr.7 = '1' ? end no suspend ? no yes read status register - toggle ce# or oe# to update status register - see status register flowchart erase suspend see suspend/ resume flowchart
p33-65nm datasheet jul 2011 78 order number: 208034-04 figure 35: block lock operations flowchart no op tion al start write 60 h block address write 90 h read block lock status locking change ? lock change complete write 01 ,d0,2fh block address write ffh any address yes write write write ( optional) read ( optional) standby ( optional) write lock setup lock, unlock, or lockdown confirm read id plane block lock status read array data = 60h addr = block to lock/unlock/lock-down (ba) data = 01h (lock block) d0h (unlock block) 2fh (lockdown block) addr = block to lock/unlock/lock-down (ba) data = 90h addr = block address offset +2 (ba+2) block lock status data addr = block address offset +2 (ba+2) confirm locking change on dq 1 , dq 0 . (see block locking state transitions table for valid combinations.) data = ffh addr = block address (ba) bus operation command comments locking operations procedure lock_op.wmf lock confirm lock setup read id plane read array
datasheet jul 2011 79 order number:208034-04 p33-65nm sbc figure 36: otp register programming flowchart start confirm data - write otp address and data yes sr.7 = '1' ? end no read status register - toggle ce# or oe# to update status register - see status register flowchart otp program setup - write 0xc0 - otp address check ready status - read status register command not required - perform read operation - read ready status on signal sr.7
p33-65nm datasheet jul 2011 80 order number: 208034-04 figure 37: status register flowchart start sr7 = '1' sr2 = '1' sr4 = '1' sr3 = '1' sr1 = '1' yes yes no yes no no no sr6 = '1' yes no sr5 = '1' no no program suspend see suspend /resume flowchart erase suspend see suspend /resume flowchart error command sequence yes yes yes error erase failure error program failure error v pen/pp < v penlk/pplk error block locked -set by wsm - reset by user - see clear status register command - set/reset by wsm sr4 = '1' yes no end command cycle - issue status register command - address = any device address - data = 0x70 data cycle - read status register sr[7:0]
datasheet jul 2011 81 order number:208034-04 p33-65nm sbc a.3 write state machine show here are the command state transitions (next state table) based on incoming commands. only one partition can be actively programming or erasing at a time. each partition stays in its last read state (read array, read device id, read cfi or read status register) until a new command changes it. the next wsm state does not depend on the partition?s output state. note: is refers to illegal state in the next state tables. table 42: next state table for p3x-65nm (sheet 1 of 3) command input and resulting chip next state (1) current chip state array read (3) word pgm setup (4,9) bp setup (8) efi command setup erase setup (4,9) befp setup (6) confirm (7) pgm/ers suspend read status clear sr (5) read id/query lock/rcr/ecr setup blank check otp setup lock blk confirm (7) lock-down blk confirm (7) write ecr/rcr confirm (7) block address change other commands (2) wsm operation completes (ffh) (40h) (e8h) (ebh) (20h) (80h) (d0h) (b0) (70h) (50h) (90h, 98h) (60h) (bch) (c0h) (01h) (2fh) (03h, 04h) other ready ready program setup bp setup efi setup erase setup befp setup ready lock/rcr /ecr setup bc setup otp setup ready n/a ready n/a lock/rcr/ecr setup ready (lock error [botch]) ready (unlock block) ready (lock error [botch]) ready (lock error [botc h]) ready (lock block ) ready (lock down block ) ready (set cr) n/a ready (lock error [botch]) n/a otp setup otp busy otp busy n/a otp busy n/a busy otp busy is in otp busy otp busy is in otp busy otp busy illegal state in otp busy otp busy n/a otp busy ready is in otp busy otp busy otp busy word program setup word program busy n/a pgm busy n/a busy pgm busy is in pgm busy pgm busy is in pgm busy pgm busy pgm susp word pgm busy is in word pgm busy word pgm busy n/a pgm busy ready is in pgm busy word pgm busy suspend pgm susp is in pgm susp pgm suspend is in pgm susp pgm busy pgm susp pgm susp (er bits clear) word pgm susp illegal state in pgm suspend word program suspend n/a word pgm susp n/a is in pgm suspend word program suspend efi efi setup sub-function setup n/a sub-function setup sub-op-code load 1 sub-op-code load 1 sub-function load 2 if word count >0, else sub-function confirm sub-function load 2 sub-function confirm if data load in program buffer is complete, else sub-function load 2 sub-function confirm ready (error [botch]) s-fn busy ready (error [botch]) sub-function busy s-fn busy is in s-fn busy s-fn busy illegal state in s-fn busy s-fn busy s-fn susp s-fn busy is in s-fn busy s-fn busy s-fn busy ready is in sub- function busy sub-function busy sub-function susp s-fn susp is in s-fn susp sub-function illegal state in s-fn busy s-fn busy s-fn suspend s-fn susp (er bits clear) s-fn susp is in s-fn susp s-fn suspend n/a s-fn susp n/a is in s-fn susp sub-function suspend
p33-65nm datasheet jul 2011 82 order number: 208034-04 buffer pgm (bp) setup bp load 1 n/a bp load 1 (8) bp load 2 if word count >0, else bp confirm bp load 2 (8) bp confirm if data load in program buffer is complete, else bp load 2 ready (error [botc h]) bp confirm if data load in program buffer is complete, else bp load 2 bp confirm ready (error [botch]) bp busy ready (error [botch]) bp busy bp busy is in bp busy bp busy illegal state in bp busy bp busy bp susp bp busy is in bp busy bp busy bp busy ready is in bp busy bp busy bp susp bp susp is in bp susp bp suspend illegal state in bp busy bp busy bp suspend bp susp (er bits clear) bp susp is in bp susp bp suspend n/a bp susp n/a is in bp susp bp suspend erase setup ready (error [botch]) erase busy ready (error [botch]) n/a ready (err botch0]) n/a busy erase busy is in erase busy erase busy is in erase busy erase busy erase susp erase busy is in erase busy erase busy n/a ers busy is in erase busy erase busy ready suspend erase susp word pgm setup in erase susp bp setup in erase susp efi setup in erase susp is in erase suspend erase busy erase suspend erase susp (er bits clear) erase susp lock/ rcr/ ecr setup in erase susp erase susp is in erase susp erase suspend n/a erase susp n/a is in erase susp erase suspend word pgm in erase suspend setup word pgm busy in erase suspend n/a word pgm busy in ers suspend n/a busy word pgm busy in erase susp is in pgm busy in ers susp word pgm busy in erase susp is in word pgm busy in ers susp word pgm busy in erase susp word pgm susp in ers susp word pgm busy in erase susp is in word pgm busy in ers susp word pgm busy in erase susp erase susp illegal state(is) in pgm busy in erase suspend word pgm busy in erase suspend is in ers susp suspend word pgm susp in ers susp is in pgm susp in ers susp word pgm susp in ers susp is in pgm susp in ers susp word pgm busy in erase susp word pgm susp in ers susp word pgm susp in ers susp word pgm susp in ers susp (er bits clear) word pgm susp in ers susp is in word pgm susp in ers susp word pgm susp in ers susp n/a n/a illegal state in word program suspend in erase suspend word pgm busy in erase suspend bp in erase suspend setup bp load 1 in erase suspend n/a bp load 1 (8) bp load 2 in erase suspend if word count >0, else bp confirm bp load 2 (8) bp confirming erase suspend if data load in program buffer is complete, else bp load 2 in erase suspend ers susp (error [botc h]) bp confirm in erase suspend when count=0, else bp load 2 bp confirm erase suspend (error [botchbp]) bp busy in ers susp erase susp (error [botch bp]) bp busy bp busy in ers susp is in bp busy in ers susp bp busy in erase susp illegal state in bp busy in ers susp bp susp in ers susp bp busy in ers susp is in bp busy in erase suspend bp busy in ers susp n/a bp busy in ers susp erase susp is in bp busy bp busy in erase suspend is in ers susp bp susp bp susp in ers susp is in bp susp in ers susp bp suspend in erase suspend illegal state in bp busy in ers susp bp busy in ers susp bp susp in ers susp bp susp in ers susp (er bits clear) bp susp in ers susp is in bp busy in erase suspend bp susp in ers susp n/a bp susp in ers susp n/a is in bp suspend bp suspend in erase suspend table 42: next state table for p3x-65nm (sheet 2 of 3) command input and resulting chip next state (1) current chip state array read (3) word pgm setup (4,9) bp setup (8) efi command setup erase setup (4,9) befp setup (6) confirm (7) pgm/ers suspend read status clear sr (5) read id/query lock/rcr/ecr setup blank check otp setup lock blk confirm (7) lock-down blk confirm (7) write ecr/rcr confirm (7) block address change other commands (2) wsm operation completes (ffh) (40h) (e8h) (ebh) (20h) (80h) (d0h) (b0) (70h) (50h) (90h, 98h) (60h) (bch) (c0h) (01h) (2fh) (03h, 04h) other
datasheet jul 2011 83 order number:208034-04 p33-65nm sbc efi in erase suspend efi setup sub-function setup in erase suspend n/a sub-function setup sub-op-code load 1 in erase suspend sub-op-code load 1 sub-function load 2 in erase suspend if word count >0, else sub-function confirm in erase suspend sub-function load 2 sub-function confirm in erase suspend if data load in program buffer is complete, else sub-function load 2 ers susp (error [botc h]) sub-function confirm if data load in program buffer is complete, else sub-function load 2 sub-function confirm erase suspend (error [botch]) s-fn busy in ers susp erase suspend (error [botch]) sub-function busy s-fn busy in ers susp is in s-fn busy in ers susp s-fn busy in ers suspend illegal state in s-fn busy in ers susp s-fn susp in ers susp s-fn busy in ers susp is in s-fn busy in ers susp s-fn busy in ers susp n/a s-fn busy in ers susp erase susp is in sub- function busy sub-function busy in ers susp is in ers susp sub-function susp s-fn susp in ers susp is in s-fn susp in ers susp s-fn suspend in ers susp illegal state in s-fn busy in ers susp s-fn busy in ers susp s-fn suspend in ers susp s-fn susp in ers susp (er bits clear) s-fn susp in ers susp is in s-fn susp in ers susp s-fn suspend in ers susp n/a s-fn susp in ers susp n/a is in phase-1 susp sub-function suspend in erase suspend lock/rcr/ecr/lock efa block setup in erase suspend erase suspend (lock error [botch]) ers susp (un- lock block ) ers susp (lock error [botch]) ers susp (error [botc h]) ers susp blk lock ers susp blk lk- down ers susp cr set n/a ers susp (error [botch]) n/a blank check setup ready (error [botch]) bc busy ready (error [botch]) n/a ready (error [botch]) n/a blank check busy bc busy is in bc busy bc busy is in bc busy blank check busy is in bc busy bc busy bc busy ready is in blank check busy bp busy befp setup ready (error [botch]) befp load data ready (error [botch]) n/a befp busy befp program and verify busy (if block address given matches address given on befp setup command). commands treated as data. (7) ready befp busy ready table 42: next state table for p3x-65nm (sheet 3 of 3) command input and resulting chip next state (1) current chip state array read (3) word pgm setup (4,9) bp setup (8) efi command setup erase setup (4,9) befp setup (6) confirm (7) pgm/ers suspend read status clear sr (5) read id/query lock/rcr/ecr setup blank check otp setup lock blk confirm (7) lock-down blk confirm (7) write ecr/rcr confirm (7) block address change other commands (2) wsm operation completes (ffh) (40h) (e8h) (ebh) (20h) (80h) (d0h) (b0) (70h) (50h) (90h, 98h) (60h) (bch) (c0h) (01h) (2fh) (03h, 04h) other
p33-65nm datasheet jul 2011 84 order number: 208034-04 notes: 1. is refers to illegal state in the next state table. 2. ?illegal commands? include commands outside of the allowed command set. 3. the device defaults to "read array" on powerup. 4. if a ?read array? is attempted when the device is busy, the result will be ?garbage? data (w e should not tell the user that it will actually be status register data). the key point is th at the output mux will be pointi ng to the ?array?, but garbage data will be output. ?read id? and "read query" commands do the exact same thin g in the device. the id and query data are located at different lo cations in the address map. 5. the clear status command only clears the error bits in the st atus register if the device is not in the following modes:1. wsm running (pgm busy, erase busy, pgm busy in erase suspend, otp busy, befp modes) 2. suspend states (erase suspend, pgm suspend, pgm suspend in erase suspend). 6. befp writes are only allowed when the status re gister bit #0 = 0 or else the data is ignored. 7. confirm commands (lock block, unlock block, lock-down block, configuration register and blank check) perform the operation and then move to the ready state. 8. buffered programming will botch when a different block addres s (as compared to the address given on the first data write cycle) is written during the bp load1 and bp load2 states. 9. all two cycle commands will be considered as a contiguous whole during device suspend states. individual commands will not be parsed separately. (i.e. if an erase set-up command is issued followed by a d0h command, the d0h command will not resume the program operation. issuing the erase set-up places the cui in an ?illegal state?. a subsequent command will clear the ?illegal state?, but the command will be otherwise ignored. table 43: output next state table for p3x-65nm command input to chip and resulting output mux next state (1) current chip state array read (3) word pgm setup (4,9) bp setup (8) efi command setup erase setup (4,9) befp setup (6) confirm (7) pgm/ers suspend read status clear sr (5) read id/query lock/rcr/ecr setup blank check otp setup lock blk confirm (7) lock-down blk confirm (7) write ecr/rcr confirm (7) block address change other commands (2) wsm operation completes (ffh) (40h) (e8h) (ebh) (20h) (80h) (d0h) (b0) (70h) (50h) (90h, 98h) (60h) (bch) (c0h) (01h) (2fh) (03h, 04h) other befp setup, befp pgm & verify busy, erase setup, otp setup, bp setup, load 1, load 2 bp setup, load1, load 2 - in erase susp. bp confirm efi sub-function confirm word pgm setup, word pgm setup in erase susp, bp confirm in erase suspend, efi s-fn confirm in ers susp, blank check setup, blank check busy status read output mux does not change lock/rcr/ecr setup, lock/rcr/ecr setup in erase susp status read array read efi s-fn setup, ld 1, ld 2 efi s-fn setup, ld1, ld 2 - in erase susp. output mux will not change bp busy bp busy in erase suspend efi sub-function busy efi sub-fn busy in ers susp word program busy, word pgm busy in erase suspend, otp busy erase busy status read ready, word pgm suspend, bp suspend, erase suspend, bp suspend in erase suspend array read status read array read id/query read status read output mux does not change status read
datasheet jul 2011 85 order number:208034-04 p33-65nm sbc appendix b conventions - additional documentation b.1 acronyms b.2 definitions and terms befp: buffered enhanced factory programming cui : command user interface cfi : common flash interface efi : extended function interface sbc : single bit per cell otp : one-time programmable plr : one-time programmable lock register pr : one-time programmable register rcr : read configuration register rfu : reserved for future use sr : status register srd status register data wsm write state machine vcc : signal or voltage connection v cc : signal or voltage level h : hexadecimal number suffix 0b : binary number prefix 0x : hexadecimal number prefix sr.4 : denotes an individual register bit. a[15:0] : denotes a group of similarly named signals, such as address or data bus. a5 : denotes one element of a signal group membership, such as an individual address bit. bit : single binary unit byte : eight bits word : two bytes, or sixteen bits kbit : 1024 bits kbyte : 1024 bytes kword : 1024 words mbit : 1,048,576 bits mbyte : 1,048,576 bytes mword : 1,048,576 words k 1,000 m 1,000,000 3.0 v : v cc (core) and v ccq (i/o) voltage range of 2.3 v ? 3.6 v 9.0 v : vpp voltage range of 8.5 v ? 9.5 v
p33-65nm datasheet jul 2011 86 order number: 208034-04 block : a group of bits, bytes, or words within the flash memory array that erase simultaneously. the p33-65nm has two block sizes: 32 kbyte and 128 kbyte. main block : an array block that is usually used to stor e code and/or data. main blocks are larger than parameter blocks. parameter block : an array block that may be used to store frequently changing data or small system parameters that traditionally would be stored in eeprom. top parameter device : a device with its parameter blocks located at the highest physical address of its memory map. bottom parameter device : a device with its parameter blocks locate d at the lowest physical address of its memory map.
datasheet jul 2011 87 order number:208034-04 p33-65nm sbc appendix c revision history date revision description jul 2009 01 initial release. apr 2010 02 update the buffered program performance, suspend latency, befp performance in ta b l e 2 6 , ?program and erase specifications? on page 58 . update the 40mhz spec for tsop package in table 24, ?ac read specifications -? on page 49 . add t dvwh timing comments in table 25, ?ac write specifications? on page 54 . reflect the program performance in cfi in table 32, ?system interface information? on page 63 . jul 2010 03 ordering information update. jul 2011 04 update tsop lead width ?b? symbol. clarify clk, wp#, we# pin description. maximum rating note clarificaiton. update table 14 eowl of latency count 2. update tsop cfi on burst read. add invalid commands clarifications on 65nm. add a note on reset in bus operation to avoid invalid commands. update micron part catalog link. correct some other minor errors.
p33-65nm datasheet jul 2011 88 order number: 208034-04

▲Up To Search▲

Price & Availability of JS28F128P33BF70

	To Download JS28F128P33BF70 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .